Month-end / Source files
For accounting practices whose clients are paid in stablecoins
Five fields for a traceable close.
Check the fields in your wallet, exchange, bank and ledger exports before the close begins. See what each file needs to carry, why it matters, and what to ask the provider when a field is missing.
Free to use. No sign-up. Field names only.
Check each export for
Five fields, explained file by file.
- An identifier for each transfer
id - The time of each transfer, with its time zone
time - The asset and the amount, with fees apart
asset, amount, fee - A reference to the invoice
invoice_ref - Any exchange rate used, with its source and time
rate
An example header row, in our field names.
- Wallet
- Exchange
- Payment processor
- Bank
- Ledger
The check
What is checked, and what it covers.
Fields checked
5
Five fields every file is checked against.
Kinds of file
5
Five kinds of file, each with its own list: exchange, wallet, payout, bank, ledger.
The list in print
1
One side of A4 holds the whole list.
01 / The fields
The detail a match rests on.
A close is traceable when every match points at the rows it rests on.
idAn identifier for each transfer
So that a match can point at the row it came from, and a changed file can be seen to have changed.
timeThe time of each transfer
With its time zone, so that a receipt lands in the right period.
asset, amount, feeThe asset and the amount
With fees shown apart from the amount received.
invoice_refA reference to the invoice
Or enough detail to tie a receipt to one invoice and not several.
rateAny exchange rate used
With its source and its time.
Start with its header row.
No client names, balances or transactions. The first line is enough to check which fields are named.
02 / The standard
The standard they are checked against
The files are the starting point. The standard is a close you can follow back to its sources.
Matches by stated rules
A close in which every match is made by a rule you can read and links to the rows it rests on.
Exceptions in the open
Rows that do not match are listed as exceptions. None is hidden and none is forced into a match.
The accountant approves
The pack goes out only after the practice's own accountant approves it, and a changed source file withdraws that approval.
What it leaves to the accountant
The accounting treatment belongs to the accountant. Web3 Close posts nothing to a ledger, certifies nothing for audit, and does not trade, hold funds or make payments.
Nothing on this page is accounting or tax advice.
03 / Your files
Different files. Different requirements.
Not every file carries all five fields. Check what is needed for each source you close from.
Read the full field listThe exchange or custody export
Always: an identifier for each row; the time of each row, with its time zone; what each row is; the asset; the amount, with its sign; fees apart from the amount. When it applies: the transaction on the chain behind a deposit or withdrawal; the reference a withdrawal carries on the bank statement; any rate a conversion was made at, with its source and time.
The wallet export
Always: the transaction each transfer is in; the time of each transfer, with its time zone; the asset, with its network and its decimal places; the amount; the sending and the receiving address. When it applies: the network fee, apart from the amount.
The payment processor's payout report
Always: an identifier for each row; the time of each row and the day its payout is due, with the time zone; what each row is: a payment, a refund, a fee; the currency of the amounts; the gross and the net amount; fees apart from the amount; the invoice each payment settles; the payout each row was paid out in. When it applies: the reference the payout carries on the bank statement; the payment a refund reverses; the transaction on the chain behind a payment taken in a token; any rate a conversion was made at, with its source and time.
The bank statement
Always: an identifier for each line; the date of each line; the amount, with its sign; the reference on each line. When it applies: the currency of the account; who paid or was paid.
The ledger export
Always: an identifier for each entry and each of its lines; the date of each entry; what each entry is: an invoice, a receipt, a credit note; the amount of each line, with debit and credit told apart; the invoice number on an invoice, a receipt and a credit note. When it applies: the transaction a receipt in a token records; the currency of each entry.
Exchange export
Wallet export
Payout report
Bank statement
Ledger export
Our names for the columns each file carries. Dashed cells are needed when it applies.
A check of your own files
A check of your own header rows
Send us the header row of each file you close from: the first line only, no client data. We reply field by field with what is present, what is missing, and what to ask the provider. There is no charge.
A header row cannot show whether a column is filled, how dates and decimals are written, or whether an identifier repeats.
Send your header rows to hello@web3close.comWhat to send
The first line only.
- 01Name the kind of file.
- 02Copy its column headings.
- 03Tell us which field was missing at your last close.
No client names, balances or transactions.
Before the next close
Start with the first row.
Check your headers against the field list. No client names, balances or transactions. An Accounting practice close pack needs its own written agreement. You pay only after all agreed packs are delivered, with source-linked matches, open exceptions, the practice accountant’s approval and the agreed before-and-after record of close time. If we do not deliver the scoped work as agreed, nothing is owed. You pay by card, in pounds, through a link sent by email after all agreed packs are delivered. Nothing is paid before that delivery. A monthly service starts only under terms agreed separately with your practice, after the first paid delivery; no standing bill starts here. The free field list commits you to nothing.
Opens in the page. Nothing to install.