Your books: ledger, statements and exports
Import an address, read every movement counted once, book each line to your chart of accounts, roll up and lock a month that ties to Arc, see the Overview, and send the files to Xero or QuickBooks.
Import an address
On the ledger page, paste an Arc address and import the last 7 or 30 days. Long histories are read in steps; press "Continue import" to read the next step now.
Every movement counted once
USDC on Arc can leave two logs for one payment. Memoline counts each movement once; here is how. Each line shows the network fee its transaction cost.
Agents and their own names
An address that is an AI agent registered in Arc’s ERC-8004 identity registry shows the name the agent gave itself, as "Agent: Scout (ERC-8004 #41)", set quieter than the names you give, and after them: your own name for an address always wins, and so does a published contract’s name. Memoline names an address only by an identity it registered itself and still owns, or by one whose agent wallet it is (set with that wallet’s own signature), and only after the chain confirms it, so a token given to someone else names nobody. An owner is named when the chain says it owns exactly one identity; a wallet named by someone else’s identity is named once Memoline has read the registry’s whole history, because only that history shows whether another identity names it too. The name is the agent’s own words, so it never goes into a Xero, QuickBooks or Memoline file; "Use this name" takes it into your address book, and from then on it is your name for the address. Names are read once a day.
Circle Gateway
A deposit into Circle Gateway (for gas-free nanopayments) is still your money, held at Circle: the line is booked to Held at Circle Gateway, an asset account the default chart makes, and the Overview leaves it out of money in and out, as it does bridges (a line you book there yourself too). Money coming back from a Gateway balance is booked there too. A chart made before this account existed gets it the first time a line is booked, unless an account already uses its code, 1910; if one does, give Held at Circle Gateway to an account yourself under Where each part of the books goes; Gateway lines booked before then move there through Rules, Book past lines, after you see what would change. Memoline shows what went to and came back from Gateway on Arc; it does not read the balance held there or the payments made from it, which Gateway settles in batches off Arc.
To see those payments, save the answer of Gateway’s searchTransfers with your own key and upload it in Settings, Circle Gateway (admins, with the two-step code). Memoline keeps the transfers to and from your accounts, checks each batch on Arc, and lists the month’s payments under the statement, summed exactly per payer and payee. They are never ledger lines and never go into your accounting files, and they are not reconciled against what you withdrew, since you withdraw when you choose. Memoline holds no Circle key and reads nothing from Circle.
Names
Give the addresses you pay a name (for example "Office rent"), and say what each is if you like: a customer, a vendor, an employee, your own wallet, an exchange or other. Names stay in your workspace and never go on-chain.
Some lines already say what they are and take no name: USDC moved between blockchains by Circle’s bridge (CCTP), such as "Received from Ethereum through Circle’s bridge", and money newly created (minted) or destroyed (burned). Known Arc contracts are named for you, with what they are.
Chart of accounts and rules
Every line is booked to an account of your chart of accounts, as in Xero or QuickBooks. Start with the default chart (sales, refunds, expenses, vendor refunds, contractor payments, network fees, bridges and transfers, internal transfers, and money held at Circle Gateway) or import your own as code,name,kind, where kind is bank, income, expense, asset, liability, equity or clearing. An account you stop using is retired, never deleted, so lines booked to it keep it.
On the chart page, Where each part of the books goes gives each fixed part of the books (sales, refunds, expenses, vendor refunds, contractor payments, network fees, bridges and transfers, internal transfers, and held at Circle Gateway) one account of its kind. An imported chart needs this: a line whose part has no account stays Uncategorised and says which part is missing. An admin or the owner changes the chart; an operator, an admin or the owner writes rules and books lines.
A line is booked by one fixed order, and the ledger says why next to each line:
- a choice someone made on that line, which nothing else changes until they go back to the rules;
- a move between two of your own accounts: Internal transfers;
- Memoline’s fee for a payout: Expenses;
- a deposit into Circle Gateway, or money back from a Gateway balance: Held at Circle Gateway;
- money moved by a bridge, or newly created or destroyed: Bridges and transfers, until someone books it;
- money to or from an own wallet you have not imported: Bridges and transfers;
- a payment to one of your payment links or invoices: Sales; its refund: Refunds, like any refund to a customer, or Sales when no account books Refunds;
- your rules, first match from the top;
- what the address book says the counterparty is (a customer’s payment is a sale, a vendor’s is an expense);
- otherwise, Uncategorised.
A transfer to yourself, and a line that is only a network fee, take no account of their own: the network fee is booked to Network fees. New lines are booked as they arrive. When you add or change a rule, past lines change only after you see what would change and confirm it; a line that changed since you looked is left as it is and reported.
Monthly statement
Opening balance, every movement, network fees and closing balance for one address and one currency, checked against the balances Arc reports. If part of the month has not been imported, the statement says so. Print it or save it as a PDF.
Rolled up by counterparty. For a month of many small payments (an agent paid per request, a service paying agents), tick "Roll up by counterparty": one line per counterparty and direction, money in before money out, the largest first, with the number of payments and their dates. Amounts are exact in the statement’s own units and are never netted; the sums are the statement’s totals. Each line opens the ledger filtered to its counterparty. The rolled Xero and QuickBooks files give each rolled line its cents from the running total, so the lines add up to the exact total rounded once and a thousand sub-cent payments lose nothing. Choose the date order your accounting software reads: it starts from your browser’s language, and year-first is for Xero only.
Close the books
Close the books locks a month once it has ended. The accounts of the workspace are the owner’s wallet and every wallet that has lines here, was imported here or sent a payout from here. A month is locked only when, for every one of them:
- every block of the month has been read by an import. Payouts made in Memoline are already in the ledger, but a payment a wallet received elsewhere is only found by reading its month. The page reads what is missing, whatever its age, while it is open: about half an hour for each account’s month, saved step by step, so you can stop and carry on later. A month read before 13 October 2026, when Memoline read only USDC and EURC, is read once more, so any other stablecoin’s movements in it are found;
- every transaction the account sent has a line, including an approval or a failed transaction that moved no money but still cost a network fee (Memoline finds them and records it);
- the statement ties to the balance Arc reports, to the unit;
- every line is booked.
Months are locked in order, in UTC, starting with the first month that has a line. Owners and admins lock a month, with a two-step code when two-step sign-in is on; checking a month with Arc can take up to five minutes. If a month cannot be locked yet, the page lists every reason with what fixes it.
Locking freezes the month’s report: every statement, the totals by account of the chart, and every line with its transaction hash, block and time. The report is a JSON file whose SHA-256 is shown on the page and kept in the action log. To check a report you hold, compute the SHA-256 of the JSON file and compare it with the one on the page: on macOS or Linux, shasum -a 256 memoline-2026-09-v1.json; on Windows, certutil -hashfile memoline-2026-09-v1.json SHA256. A CSV made from the same report is offered too; its first row shows the JSON file’s SHA-256, and the CSV file’s own SHA-256 is different.
In a locked month no line can be booked again, changed or deleted. Payments, imports and everything else keep working. A line that arrives later for a locked month (for example from a wallet imported afterwards) is kept at its true date and listed in the next month’s report as an adjustment; book it before the next month is locked, because that lock freezes it too. When the other side of such a line sits in a locked month booked to a different account, the report names that month and account, so the correction can be posted knowingly.
Only the owner can unlock, only the last locked month, and only with a reason. The old report and its hash are kept and listed under the month; locking again makes a new version that names the one it replaces, so anyone holding the old file will need the new one.
Coming up
At the top of the Overview, Coming up shows what your payouts will take from each wallet in the next 31 days, in your workspace’s time zone, and what each wallet holds now, read from Arc at its newest block, which the page names with the time it was made. It counts the payments of payouts waiting to be sent (queued, or sent and not yet on Arc at that block) with the fee each already carries, and the days of your schedules that are not made yet, overdue ones included, with Memoline’s fee at most (the free payments go to whichever payout is made first). A paused schedule is listed and not counted; one that has ended is not listed. Payments that need attention are named beside their payout and not counted until you retry them.
Each wallet says whether it covers what is due; only just, when it would keep less than about 0.01 USDC a payment as room for the network fees paid when you sign; or is short: by how much from the first payout it cannot cover, and what all 31 days need more. A wallet that would keep too little USDC to send anything is short for network fees, even when it holds every payment. USDC and EURC are never added together, and Memoline’s fee is always paid in USDC, so a EURC payout needs USDC too. It is a forecast: the check before you sign is the one that counts, and money you expect to receive is not counted. A wallet that also pays, in the next 31 days, for another of your workspaces says so, and its Covers badge is shown amber rather than green, since what covers here may not cover there too; view the workspaces together to count everything. Wallets that pay but are not in your books are listed with a link to import them. The same figures are in the API at GET /api/v1/upcoming.
Overview
The Overview shows money in and out by month, one stablecoin at a time (no two are ever added together, even two of one currency), in UTC months, for the last 3, 6, 12 or 24 months and this one. Money in and out leave out what moved between your own accounts, and what went across bridges and exchanges that a person has not booked yet, each shown on its own line below the chart. Network fees are counted on every line and shown apart; for USDC, net is after them.
Balances at each month’s end come from Arc, never from the ledger: a locked month’s from its report, an ended month’s read at its last block, and the balance now at the newest block, each with the block it is of, so anyone can read Arc at that block and compare. Each ended month says whether its lines tie to the change of that balance. Runway is the balance now over how fast the total balance fell in the last three full months of books; it counts what left by a bridge or an exchange whatever it was booked to, and waits until three full months have ended after the month the books start in. Below are who paid you and who you paid most, where moved money went, the totals by account of the chart, and the invoices still owed. Every chart has its figures as a table.
Several workspaces together
If you belong to more than one workspace, open View together with your other workspaces on the Overview and tick the ones to add, up to 10 in all. You only see workspaces you are a member of; one you are not in is refused, whether it exists or not.
The open workspace comes first, then the others in the order you tick them, and the order decides two things: a line that more than one of them holds (the same account, transaction and log) is counted once, booked as the first workspace in the list that holds it books it; and network fees go to the first one’s Network fees account. Each account, and its balance, counts once.
A payment between accounts of two of the workspaces is a move between them: it is left out of money in and out, and shown on its own line with both sides, so a side that is not imported yet shows as a difference. Each workspace keeps its own locked months, so a late line counts where its own workspace’s report lists it. A month before a workspace’s books start leaves that workspace out, and is checked against Arc only for the others; the table says how many of the workspaces locked each month. Invoices owed are shown when one workspace is viewed.
Exports
Download CSV files for Xero or QuickBooks bank statements, or a plain CSV. Amounts are rounded once so the totals match to the cent; a yen, won or Chilean peso stablecoin is rounded to whole units, since those currencies have no cents. For a stablecoin with 18 decimals, such as BRLA, the plain CSV gives each line’s exact amount in amount_exact (with token_decimals) and its exact totals in the footer’s _exact keys, and the Xero and QuickBooks files round its exact amounts once. In the Xero and QuickBooks files, Memoline’s fee for a payout is a payment to Memoline, and each line’s description ends with the account it is booked to, such as "Booked to 5200 Contractor payments", after the reference and the name, so a bank rule can code it. A plain CSV that holds several stablecoins gives each its own totals; they are never added together.