Pay-In
Money that arrives knowing why.
Incoming funds matched to payer, reference, and invoice, so finance can identify, reconcile, and act on every receipt.
Incoming paymentRECEIVED
AMOUNTEUR 86,400.00
PAYERNORDWERK GMBH
REFERENCEINV-2041
MATCHED TOCUSTOMER · INVOICE
NEXT ACTIONHOLD · CONVERT · PAY OUT
RECONCILED
The allocation flow
From arrival to allocation.
01
Payer pays your Local Business Account
Local details in GBP, CAD, EUR, USD, or AED. Your payer sends a domestic transfer on local rails, nothing international about it from their side.
02
Reference captured
Payer name, reference, invoice, and expected amount are matched as the funds land.
03
Funds identified
Attributed to the right customer, invoice, or commercial event, not left as an unexplained credit.
04
Allocation decision
Hold the balance, convert at your pre-agreed FX margin, allocate internally, or prepare a supplier payout.
✓
Record updated
References, payer context, allocation status, and evidence stay on file for reconciliation and follow-up.
Why it matters
Arrived is not the same as useful.
Finance needs to know who sent the funds, what they relate to, whether the amount matches, and what happens next. That is the difference between a credit and a reconciled receipt.
Identify the payer
Funds linked to payer name, purpose, reference, and expected activity.
Match the event
Connected to the customer, invoice, funding instruction, or treasury need.
Prepare the next action
Convert, hold, allocate, or prepare the payout, decided with context.
Support the records
Clean pay-in data means balances that can be explained later.
Where it gets messy
The receipts that ruin a month end.
The goal is not only to receive funds. It is to receive funds the business can identify, explain, reconcile, and use.
!Missing or unclear payer reference
!Payment sent from a different account name
!Amount arrives different from expected
!Intermediary deductions or routing charges
!Multiple customers paying into similar flows
!Finance cannot match funds to an invoice
!Funds arrive before the FX or payout instruction is clear
!Compliance review delays onward movement
Built-in invoice generator
The invoice carries your receiving details.
Add your counterparties once, then generate invoices inside Unicorn Currencies. Pick the currency, and the invoice carries the matching Local Business Account details, so your customer pays locally and the receipt arrives pre-matched to the invoice.
✓Counterparties stored with beneficiary and invoice context
✓Choose the currency, get the right local details on the invoice
✓Incoming funds reconcile against the invoice automatically
Invoice INV-2041EUR
BILL TONORDWERK GMBH
AMOUNTEUR 86,400.00
PAY TOYOUR EUR ACCOUNT
IBANDE89 3704 0044 0532 0130 00
RAILSSEPA · SEPA INSTANT
Where Pay-In sits in your flow
LOCAL BUSINESS ACCOUNT
Payer sends a domestic transfer to your named local details
PAY-IN · YOU ARE HERE
Funds identified, matched, and allocated
FX
Conversion at a pre-agreed FX margin
PAY-OUT
Supplier payment routed
PLATFORM
Records stay connected
Before funds arrive
Set the context first.
The cleaner the expected-payment context, the faster funds become usable.
✓Expected payer name
✓Expected amount and currency
✓Payment reference
✓Invoice or commercial reason
✓Customer or supplier context
✓Purpose of payment
✓Onward action: hold, convert, allocate, or pay out
✓Supporting documents where required