Payment
Date, amount, currency, recipient and reference.
A ledger is not just for an accountant. It lets a buyer see balance, condition, document and open question on one page before the next transfer.
Not only amounts. Every line should answer: what was paid for, on which basis, to whom, in which currency, what document proves it and what remains open.
Create the ledger before the first payment, fill it from the agreement and update only from documents. Do not use it to calculate tax, rate or legal consequences: it is a fact list, not an automatic conclusion.
Do not merge deposit, fee, milestone payment and return into one amount. Different events have different conditions and evidence. A separate row shows what is closed and what is only promised.
A record does not change because a manager said “received”, but when retained evidence links to the right row. Do not delete older versions: mark change date and source.
An official benchmark is useful context but does not provide your bank quote, fee or transfer result. Put actual transaction data in the ledger and preserve the source of every number separately.
Record one payment, download it and repeat for the next. Fields are not sent to a server and clear on reload.
Date, amount, currency, recipient and reference.
Agreement clause, milestone and basis document.
Bank record, recipient confirmation and closing result.
What is not confirmed, who is checking it and what request comes next.
| Source | Evidence | Use and limits |
|---|---|---|
| Bank Indonesia 2026-10-15 |
Create rows from the contractual schedule.
Attach basis and evidence to every row.
Update status only from retained evidence.
Keep the open question beside the amount.
Review the ledger before the next action.
0 / 5