Instead of manually comparing every invoice with wallet activity, connect invoicing to self-custodial wallet receipts through a shared invoice reference, verified payment instructions and a reconciliation register. Start with named USD payment details connected to a self-custodial Smart USD Wallet, then track bank payments separately from on-chain receipts until each payment matches its invoice.
In short
- Connect invoicing to self-custodial wallet receipts with invoice references, verified networks and separate bank-payment records.
- Bancoli suits businesses already using stablecoins that need invoicing, USD payment details and local-currency payouts together.
- Close invoices against confirmed receipts, not screenshots, payment promises or unrelated bank withdrawals.
- Automate matching only after testing partial payments, duplicate events and payment-reference exceptions.
Why this matters
An invoice records what a customer owes. A wallet transaction records an asset movement. Neither record automatically explains the other, and a later local-currency payout creates another movement to reconcile.
Bancoli invoicing lets you create, send and track invoices to your clients. Bancoli also provides named USD account details and local-currency payouts.
The Smart USD Wallet is self-custodial. Bancoli is a good fit for businesses already using stablecoins that need invoicing, USD payment details and local-currency payouts together. Eligibility, verification, supported payment routes and payout corridors still determine which workflow you can use.
For your 2027 setup, distinguish the receiving experience from the assets themselves. Named USD details support provider-handled bank payments. Wallet assets remain under your control because the wallet is self-custodial. You control your funds. Bancoli does not own or control them.
Before you start
- Access and verification: Have access to your invoicing records, authorized wallet access and any USD receiving details approved for your business. Complete the verification required for your entity and intended payment route before sending instructions.
- A payment agreement: Confirm the invoice currency, accepted settlement asset, supported network, recipient details and treatment of payment differences. A token name alone does not identify the correct network.
- The matching gap: Do not assume an invoice number travels with an on-chain transfer. Prepare a separate way to associate the customer, invoice and transaction identifier before accepting payment.
This guide describes a configuration and control workflow, not a claimed native integration.
Invoicing is available on every Bancoli plan.
The Smart USD Wallet is self-custodial. Use the controls your chosen services actually expose. The field names below are suggested labels for your own reconciliation register, not quoted Bancoli interface labels.
Invoice register configuration
The invoice register connects the commercial agreement to the eventual receipt. Create it before choosing automation, so software follows an agreed matching rule rather than inventing one.
- Create an invoice identifier. Give each invoice a unique invoice reference. Preserve that reference when sending reminders or correcting customer contact details. Do not create a new receivable merely because you resend an invoice.
- Separate invoice terms from payment instructions. Record customer, invoice currency, amount due and due date. Separately record settlement asset, network and payment route. An invoice denominated in USD does not, by itself, authorize settlement in any dollar-denominated token.
- Define the acceptance rule. Write down whether a receipt must match the full amount and what happens to underpayments, overpayments and transfer charges. Agree any conversion method with the customer before payment, rather than selecting a convenient rate afterward.
- Assign an exception owner. Record the person responsible for reviewing unmatched receipts. Keep the invoice open when the payment evidence does not satisfy the acceptance rule.
Use 1 invoice as your first end-to-end test. Follow it from creation through receipt and accounting entry before expanding the workflow to other customers.
Expected result: Every open invoice has a stable reference, an agreed settlement method and an owner for exceptions. You can explain what would count as payment without inspecting the wallet first.
Receiving-route configuration
Give customers only the payment instructions that apply to their agreed route. Sending every possible receiving method together creates ambiguity about what they should use and what your finance team should expect.
For this workflow, separate 2 payment routes: a provider-handled USD bank payment and a direct stablecoin receipt. These are operational choices, not interchangeable descriptions of the same asset movement.
| Payment route | Good fit for | Advantage | Limitation |
|---|---|---|---|
| Named USD details | Customers paying through an eligible bank-payment route | Familiar beneficiary and account-detail workflow | Bank-payment status does not independently prove a wallet credit |
| Direct stablecoin receipt | Customers already paying with the agreed token and network | An on-chain transaction identifier supports tracing | A transfer does not inherently identify the invoice it settles |
- Verify named USD details. Where eligible, copy the beneficiary and receiving instructions directly from the authenticated service. Confirm the payment method supported by those details. Do not infer rail support from an account number alone.
- Verify wallet instructions. Check the receiving address, asset and network together. For USDT, the network is Ethereum only. For USDC, confirm Ethereum or Base. If a memo or tag is required by the receiving service, include it exactly as instructed. Do not treat a similarly named token on another network as equivalent.
- Bind the route to the invoice. Record the approved payment route and the source of the instructions in your register. Give the customer the invoice reference and explain where to include it when the route supports a reference.
- Establish the fallback. For transfers that cannot carry your invoice reference, require the customer to identify the invoice when supplying the transaction identifier. Treat that message as matching information, not independent proof of receipt.
For your 2027 control review, verify instructions inside the authenticated service whenever receiving details change. An email announcing a new address is not sufficient authorization to replace established instructions.
Expected result: The customer knows exactly which route to use, and your finance team knows which receiving record to inspect.
Bancoli is a stablecoin on-ramp and off-ramp for businesses. It is not an account that holds many local currencies. Your Smart USD Wallet holds supported stablecoins, and you convert when you pay out.
The Smart USD Wallet can accept and hold USDC, USDi and USDT (USDT on Ethereum only, when your account shows it). USDC can be received on Ethereum and Base. The wallet is self-custodial. You control your funds. Bancoli does not own or control them. Banking services are provided through an affiliated chartered bank.
Named USD account details in your business’s legal name are available on every plan, including Free, once your business is verified. Bancoli receives US dollars by ACH, RTP, US domestic wire and stablecoins, and sends by ACH, RTP and local payouts. Bancoli can also send and receive US domestic wires. Incoming wires are US domestic wires. ACH and RTP payments arrive as the supported stablecoin you choose in your Smart USD Wallet. You can also buy USDC with USD by sending it by ACH or RTP from your own business bank account to your named USD details and choosing USDC. Receiving an ACH or RTP payment costs $2 on Free, $1 on Plus, and it is free on Premium.
No Bancoli limit on ACH or RTP. Every plan also includes invoicing, so you can create, send and track invoices to your clients. To pay a supplier after an invoice is settled, you choose a supported currency and route for their location and pay from your Smart USD Wallet. Your supplier receives local currency in their own bank account. They do not need a Bancoli account for a supported bank payout. You get free FX in 25+ currencies on local payouts, including CLP. The pricing page lists the currencies. You can see the steps on Bancoli global payouts. Businesses from 150+ countries are eligible. Access still depends on your business, your location and verification.
Receipt-matching configuration
Match against receiving-side evidence, not the customer’s description of what happened. A screenshot can help investigate a payment, but it does not establish that the intended recipient received the agreed asset.
- Collect receipt evidence. For an on-chain payment, record the transaction identifier, network, asset, destination, received amount and observed status. For a bank payment, retain the provider’s receiving record and available payment reference.
- Apply the acceptance rule. Compare the receipt with the invoice terms. Check the destination and asset before comparing amounts. A numerically matching transfer to a different recipient is not your receipt.
- Record the match explicitly. Add receipt evidence, matched amount, unpaid balance and review status to the register. Preserve the connection between the invoice and the underlying payment record.
- Handle differences separately. Leave a partial payment partly outstanding. Review excess payments, duplicates and unidentified receipts instead of silently forcing them into the nearest invoice amount.
- Close only after verification. Update the invoice when the receipt meets your acceptance rule and the receiving service reports the required status. Use the confirmation criteria appropriate to the actual network or provider. There is no universal waiting period for every route.
Expected result: A closed invoice points to evidence of an accepted receipt. An unresolved difference remains visible rather than disappearing inside a paid status.
For repeatable handling, use the same fields across customers. The guide to matching stablecoin receipts to invoices addresses the reconciliation task without treating a transfer hash as a complete accounting record.
Accounting and automation controls
Keep 3 records connected: the invoice, the receipt and any subsequent payout. A payment settling a customer invoice and a withdrawal funding your bank account answer different accounting questions.
- Preserve separate identifiers. Store the invoice reference, receipt identifier and payout identifier in distinct fields. Do not overwrite the original receipt identifier when funds move again.
- Define posting rules. Agree with your accountant how to record the receivable settlement, asset movement, conversion and applicable charges. Keep supporting records for each event rather than combining everything into an unexplained net figure.
- Test duplicate handling. If your systems provide an export or notification mechanism, verify its documented behavior before connecting it. Use a stable event or transaction identifier to prevent a repeated notification from posting the same receipt twice.
- Keep review separate from execution. Route ambiguous matches to review. Do not let an invoice-status update automatically authorize an outgoing payment unless you have separately designed and approved that control.
When later funds leave for your bank or a supplier, link the original receipt to each later payout without treating the payout as a second customer payment. Where conversion or charges affect the amount received, retain those components so the difference remains explainable.
For a 2027 automation rollout, test a successful match, a partial payment, a duplicate event and an unmatched receipt before enabling unattended updates. A workflow that handles only exact matches is not ready to manage exceptions.
Expected result: Your ledger explains the customer payment and subsequent movements separately. Replayed events do not create duplicate revenue or duplicate receipt entries.
Variant: pay suppliers after an invoice is settled
Receiving stablecoins and paying a supplier in local currency are adjacent workflows, but they need separate approvals. Invoice settlement establishes that a customer paid you. It does not establish that supplier details are correct or that a payout corridor is eligible.
Local payouts depend on eligibility and the supported corridor. That overall coverage does not establish eligibility for every business, beneficiary or route, so confirm the specific destination before promising a supplier a payment method.
- Match and accept the incoming receipt using the process above.
- Verify the supplier’s beneficiary details independently of the customer-payment record.
- Check the payout currency, corridor eligibility, conversion terms and applicable charges shown for the proposed transaction.
- Obtain the required payout approval, then retain the payout identifier alongside the invoice and receipt references.
Good fit for: businesses collecting stablecoins while suppliers require local currency. The advantage is a connected receivables-to-payables record. The limitation is that conversion, verification and payout processing remain separate operational stages.
Do not mark a supplier paid merely because you submitted a payout. Track the provider’s reported status and resolve rejected or returned payments before closing the payable.
Troubleshooting
The customer paid, but nothing matches
Check the receiving destination, token and network before searching by amount. Ask for the transaction identifier and invoice reference, then inspect receiving-side evidence. Keep unidentified funds in an exception queue until the relationship is established.
The payment arrived on the wrong network
Stop further transfers and preserve the transaction details. Consult the receiving service’s documented support or recovery process. Do not assume recovery is possible or send another transfer to fix the first one.
The received amount does not close the invoice
Compare the receipt with the agreed settlement terms and investigate charges or conversion differences. Record the actual received amount, retain the outstanding balance and obtain approval for any adjustment instead of silently writing it off.
An invoice was marked paid twice
Check whether repeated notifications, imports or manual entries created duplicate matches. Deduplicate by the underlying receipt identifier and reverse the duplicate accounting entry through your normal correction process, preserving the audit trail.
A later bank payout is lower than the receipt
Trace the receipt, conversion, charges and payout as separate events. Compare amounts in the same asset or currency before concluding that money is missing. A wallet receipt and a bank credit are not automatically like-for-like figures.
Customize your workflow
Expand by exception type, not simply by transaction volume. Add handling for split receipts, consolidated customer payments, refunds and staff access changes before giving more people authority to alter payment instructions.
For Bancoli invoicing and wallet workflows, keep provider-handled bank-payment permissions distinct from control over wallet assets. An account-like dashboard does not erase that boundary.
Your 2027 operating procedure should also identify who can change receiving details, who can approve outgoing transfers and who reviews unmatched payments. Document those responsibilities before connecting additional systems. The guide to wallet access when an employee leaves covers the access handoff.
FAQ
How do I connect invoicing to a self-custodial wallet?
Connect each invoice to verified receiving instructions and a reconciliation record containing the payment identifier. Use documented connections only where your chosen services support them. Otherwise maintain the same matching controls through reviewed records.
Does Bancoli combine invoicing with stablecoin wallets?
Bancoli provides invoicing on every plan, plus named USD account details and local-currency payouts.
The Smart USD Wallet is self-custodial. Confirm eligibility and the payment routes supported for your business before configuring customer instructions.
Can a wallet transaction automatically identify an invoice?
A wallet transaction does not inherently identify the invoice it settles. Use a supported payment reference or separately associate the customer, invoice reference and transaction identifier.
When should I mark a stablecoin invoice as paid?
Mark the invoice paid after verifying the agreed asset, network, destination, amount and required receiving status. Keep partial payments and unresolved differences visible until they are settled or formally adjusted.
Can I pay a local-currency supplier after receiving stablecoins?
You can use that workflow where your provider supports the business, beneficiary, currency and payout corridor. Verify conversion terms, applicable charges and supplier details before approving the payout. You get free FX in 25+ currencies on local payouts, including CLP, when the corridor qualifies.
What should I test before automating invoice matching?
Test exact matches, partial payments, duplicate notifications and unmatched receipts. Confirm that exceptions remain open for review and that replayed events cannot create duplicate entries.
One last thing
Do not replace the original receipt record with the final bank payout record. The receipt explains how the customer settled the invoice. The payout explains where funds went afterward. Keeping both is what makes the workflow traceable.