Invoices
Numbered invoices with line items, paid wallet to wallet, marked paid when Arc shows the payment, with reminders and recurring invoices.
Making an invoice
In Invoices, New invoice: choose or add the customer, the currency (USDC or EURC), the lines, an optional tax rate and the due date. The total is worked out exactly as you type: each line is quantity times unit price, rounded half up to 6 decimals, and tax is worked out once, on the subtotal.
Where your country asks for them on an invoice, put your business address and tax number in Settings, Invoices: they print under your name, and each invoice keeps them as they were when it was issued.
Save it as a draft to change it later, or issue it. Issuing gives the invoice its number (for example INV-0001; change the prefix in Settings, Invoices) and a payment link for the total. Numbers are never reused, and a failed issue uses none.
What an invoice shows
A Memoline invoice is a request for payment. Where VAT, GST or e-invoicing rules apply to you, the invoice the law asks for must come from software that meets those rules; you can attach the Memoline invoice to it, with its pay link.
Besides the lines and the totals, an invoice can carry:
- Customer tax ID: your customer’s tax number, such as a VAT number, entered when you add the customer. It prints under their name.
- Tax shown as: what the tax line is called, Tax, VAT, GST or Sales tax, chosen next to the tax rate. Only the word changes; the rate and the amount stay the same. A recurring invoice gives its choice to every invoice it issues.
- Date of supply: the day the goods or services were supplied, when it is not the issue date. It prints under the issue date. It belongs to one invoice, so a recurring invoice never copies it.
- Your name, address and tax number as they were when the invoice was issued. Renaming the workspace later never changes an issued invoice; a draft shows them as they are now.
Once an invoice is issued, its dates are fixed. To change them, void it and issue a new one.
Getting paid
Send the customer the pay link, or show them the QR code. They pay from their own wallet on Arc; only the invoice number is written on Arc with the payment. The pay page shows them the invoice, which they can print or save as a PDF. It shows the invoice as issued to anyone with its link, including your customer’s name, billing address and tax id.
The invoice is marked part paid, paid or overdue from the payments Arc shows and the due date. A payment reported twice counts once. An overdue invoice can still be paid through the same link; the payment is marked as late. One invoice can ask for up to 1,000,000 USDC or EURC, the most one pay link takes.
If you refund a payment from the invoice’s payment link, the refund counts once it is confirmed on Arc. A refund of only an overpayment leaves the invoice paid. A refund that leaves less than the total received marks the invoice refunded: it is no longer chased, and if anything is still due you void it and issue a new one.
Invoices in your client’s currency
An invoice can be priced in one of 54 currencies (rupees, pesos, naira, shillings, yen and more) and paid in USDC or EURC. In New invoice, choose the currency in Price in and the token in Paid in. The lines, the tax and the total are in that currency, in its own units: whole yen, two decimals for rupees, three for dinars. 1 USDC is taken as 1 US dollar and 1 EURC as 1 euro, so an invoice in US dollars paid in USDC is an ordinary USDC invoice. While you write it, the form shows what the total comes to in the token at today’s rate, and warns you when that is near the 1,000,000 one payment can carry.
When your client opens the pay page, Memoline quotes the token amount at the day’s published rate from Exchange Rate API, checked against the European Central Bank’s rate where it publishes one, and holds that amount for 30 minutes. The page shows the price, the rate, its source and its day, and until when the amount holds, before the wallet is asked. The amount is rounded up to the token’s smallest unit, so at that rate you never receive less than your price. If the day’s rate is more than a day and a half old, moved more than 25% in a day, or is more than 5% from the European Central Bank’s, no quote is made and the page says why.
A payment of the quoted amount within its 30 minutes, or within 10 more for a transaction signed in time, pays what it was quoted for. Another amount sent while a quote holds is valued at that quote’s rate. A payment that arrives outside every quote is recorded in the token, the money that moved, and named on the invoice; Memoline will not guess its value in your currency, so it is not counted toward the price. A remainder too small to quote, under 0.001 of the token, reads paid.
Your books keep the token amount, with the price, the rate, its source and its day as the line’s note. A refund sends back the token and counts against the price in proportion to the payment it refunds. Memoline exchanges nothing and holds nothing: your client pays the token from their own wallet straight to yours. A plain transfer cannot pay such an invoice, since it has no quote, and neither can a smart-contract wallet: your client pays from an ordinary wallet on the pay page. Rates By Exchange Rate API.
Voiding
Void an issued invoice with a reason; its pay page closes. A paid invoice cannot be voided, since its payment is in your books: refund the payment instead if it should not stand. The invoice keeps its number. A payment that was already on its way still arrives: the invoice shows it was paid after it was voided, it counts once in your books, and you can refund it from the payment link.
Still owed
The Invoices page shows what is still owed, by currency, bucketed by how many days late it is. It checks every invoice’s received amount against the payments in your books and says if anything differs.
Reminders
Turn on reminders in Settings, Invoices. A customer with an email address gets at most one reminder in each window: in the 3 days before the due date, in the week from the due date, in the second week after it, and from two weeks to a month after it; until the invoice is paid or void. A reminder sent after the due date says the invoice is overdue. Reminders need the operator’s email sending to be set up; until then the page says they cannot be sent. You also get one notification when an invoice becomes overdue. Before either, Memoline reads Arc for payments to the invoice’s pay link that nobody reported; when Arc cannot be read that day, the reminder and the notification wait for a later day, so a customer who paid is never asked again.
Recurring invoices
In Invoices, Recurring: choose a customer, lines and a schedule (every month on a day from 1 to 28, or every few weeks). Each cycle Memoline issues a new invoice with its own number and pay link, so a payment for one month can never settle another. Pause or resume at any time. Cycles that fall while it is paused are skipped, never billed later; a cycle on the day you resume is still issued. If an invoice cannot be issued on its day, Memoline tries again on the next run, with a due date counted from the day it is issued, and it still counts toward the number of invoices you set.