← Journal · Invoicing & Payments · · 12 min read

PayNow Invoice Automation: Workflow and Controls

Adding a PayNow QR code to an invoice makes payment easier. Automating the full workflow means identifying the invoice, confirming settlement, reconciling it once, and stopping reminders safely.

By , a service of Synergy Accounting Pte Ltd, a Singapore CA practice serving SMEs.

Adding PayNow to an invoice is easy.

Automating what happens after the customer pays is the harder part.

A static QR code or UEN can move money into the correct bank account, but the finance team may still need to work out which invoice the receipt belongs to. A customer can omit the reference, combine three invoices into one transfer, pay a partial amount, or type the invoice number incorrectly.

The useful goal is not merely “accept PayNow.” It is:

Invoice issued
→ customer selects PayNow
→ payment carries an invoice-specific reference
→ receipt is confirmed
→ payment is matched once
→ invoice status is updated
→ reminders stop
→ exceptions enter a review queue

This guide explains three levels of PayNow invoice automation and the controls needed around matching, reconciliation, fraud, and customer communication.

Product features, fees, limits, and bank procedures change. Confirm the current position with your bank, accounting platform, and payment provider before implementation.

What is PayNow Corporate?

PayNow Corporate allows an eligible business to link its bank account to a corporate proxy, normally its UEN or a UEN with an approved suffix.

Customers can then pay the business through participating banking applications without entering the full bank-account number. Payment can be initiated using the UEN, supported account details, or a QR code, depending on the bank and payment setup.

The Association of Banks in Singapore publishes a PayNow fact sheet, while each participating bank controls its own registration, user access, notifications, transaction limits, and business-banking procedures.

PayNow Corporate is the payment rail. It does not automatically create good invoice data, allocate every receipt, or update your accounting system. Those capabilities come from the surrounding workflow.

Three levels of PayNow invoice setup

Level 1: UEN or static QR on the invoice

The simplest setup prints:

This can work for a small invoice book.

The advantage is low complexity. The customer scans or enters the UEN, verifies the recipient, types the amount and reference, and pays.

The limitation is reconciliation. Static payment details may not encode the amount or a unique invoice reference. Matching depends on what the customer types and what appears in the bank feed.

Use this approach when:

Do not describe this as fully automated. It is payment convenience with manual exception-heavy reconciliation.

Level 2: Invoice-specific dynamic QR

A dynamic QR can carry transaction-specific information such as:

The customer scans a code created for that invoice. Because the payment carries a structured reference, software has a better basis for matching the receipt.

Dynamic does not mean infallible. Your system still needs to handle:

Use this approach when matching effort is the main problem and the chosen bank or payment provider supports the required data flow.

Level 3: PayNow through an online invoice payment integration

Some accounting platforms connect online invoices to payment providers that support PayNow. The customer opens the invoice, selects a payment option, and follows a provider-hosted flow.

The provider can return transaction data to the accounting platform, reducing manual matching. Xero's current Singapore payment materials, for example, describe PayNow availability through supported providers and invoice payment data flowing back for easier reconciliation. Check the current Xero Singapore payment options rather than assuming every provider or plan behaves the same way.

This approach can offer the cleanest customer and finance experience, but it introduces:

“Connected to accounting” does not necessarily mean “reconciled perfectly.” Test how gross payment, fees, net settlement, and invoice status appear.

The complete PayNow invoice workflow

Step 1: Register the correct business entity

Register PayNow Corporate through the business's bank using the correct legal entity and UEN.

If the group has several companies, do not reuse one company's payment identity on another company's invoices because the same finance team manages both. The invoicing entity, payment recipient, bank account, and accounting organisation should agree.

Document:

Step 2: Choose the matching method

Decide what links a payment to an invoice.

Options include:

Do not rely on amount alone. Two customers can pay SGD 1,000 on the same day.

Define a matching hierarchy:

  1. Exact unique reference and expected amount
  2. Exact unique reference with partial or excess amount
  3. Customer identity plus amount and open invoice
  4. Other plausible matches sent for review

Only high-confidence cases should post automatically.

Step 3: Put clear payment instructions on the invoice

Show:

Tell the customer to verify the registered recipient name displayed in their banking application before authorising payment.

Avoid asking customers to send screenshots as the primary proof of payment. A screenshot can help investigate, but your bank or payment-provider record should determine whether funds were actually received.

Step 4: Receive a trusted payment event

The workflow needs a dependable source of payment status.

Depending on the setup, that may be:

Distinguish:

Do not mark an invoice paid merely because the customer clicked a button or a browser returned to a success page.

Step 5: Match the receipt

For a high-confidence match:

  1. Confirm the transaction has not already been processed
  2. Confirm entity and currency
  3. Confirm amount
  4. Confirm unique invoice reference
  5. Apply the payment to the open invoice
  6. Record the provider or bank transaction ID
  7. Send the case to reconciliation

For anything ambiguous, create an exception rather than guessing.

Step 6: Reconcile gross payment, fees, and settlement

Payment integrations can create a difference between:

For example, a customer may pay an invoice for SGD 1,000 while the provider deposits a lower net amount after fees. The invoice may still need to show SGD 1,000 paid, with the fee recorded separately.

Design the accounting flow with your accountant or bookkeeper:

Do not force the invoice to match the net bank deposit by quietly reducing the customer payment.

Step 7: Stop reminders safely

Once a trusted payment record is applied, the invoice leaves the reminder sequence.

If the customer says they paid but the receipt is not found:

  1. Pause reminders temporarily
  2. Ask for payment date, amount, recipient name, and reference
  3. Search bank and provider records
  4. Resolve the mismatch
  5. Resume only if payment was not received

This avoids sending an overdue reminder immediately after a genuine payment.

Our guide to AR automation explains why stopping correctly is as important as sending on time.

Exception handling

A reliable workflow expects messy payments.

Missing or incorrect reference

Search using customer, amount, and timing. If more than one invoice is plausible, route it to a person.

Partial payment

Apply the received amount according to approved accounting rules. Keep the balance open and adjust the reminder language so it acknowledges the partial payment.

Combined payment

Allocate one receipt across several invoices only when the remittance or other evidence makes the allocation clear.

Overpayment

Do not invent an allocation. Record the overpayment or credit according to the accounting policy and notify the responsible employee.

Duplicate payment

Flag the second receipt. A person should verify whether it is genuinely duplicated and decide whether to refund or hold it as a credit.

Payment to the wrong entity

Escalate immediately. Do not casually move money between related companies without documenting the correct accounting and legal treatment.

Invoice changed after QR generation

Invalidate or replace the payment request where the provider supports it. If the original code remains usable, define how incorrect amounts will be handled.

Provider says paid, bank settlement is missing

Keep the payment and settlement statuses separate. Investigate before treating the bank deposit as complete.

Fraud and security controls

Payment convenience must not weaken verification.

Protect changes to payment details

Restrict who can change:

Require approval for sensitive changes and keep an audit history.

Use multi-factor authentication

Enable strong authentication for banking, accounting, email, and payment-provider accounts. Remove access promptly when roles change.

Verify recipient identity

Invoices should state the expected registered recipient name. Customers should verify the name displayed by their bank before approving payment.

Treat email template changes as financial changes

An attacker who can replace an invoice QR code or payment button can redirect money without changing the ledger. Monitor and approve template modifications.

Validate provider events

If software receives payment webhooks:

Idempotent processing means the same provider event can arrive more than once without creating duplicate payments.

Separate preparation and approval

Where practical, the person who changes payment configuration should not be the only person who approves and verifies it.

Reconcile independently

Compare provider records, accounting entries, and bank settlements. No single dashboard should be treated as unquestionable.

How to test PayNow invoice automation

Use a controlled test set:

  1. Exact full payment
  2. Partial payment
  3. Overpayment
  4. Missing reference
  5. Incorrect reference
  6. Combined payment
  7. Duplicate provider event
  8. Duplicate customer payment
  9. Refund
  10. Failed or delayed settlement
  11. Invoice amended after payment request
  12. Payment claimed but not found

For each, verify:

Test in a non-production environment where possible. If live testing is necessary, use small controlled invoices and document every step.

What to measure

Track whether the workflow reduces finance work and payment friction:

The best measure is not PayNow adoption by itself. It is the share of payments that move from customer to reconciled invoice without avoidable manual work or control failures.

A practical rollout

Phase 1: Static details with disciplined references

Add verified PayNow Corporate details and clear invoice-reference instructions. Measure how many receipts still need manual matching.

Phase 2: Dynamic references or QR codes

Introduce invoice-specific payment data where matching effort justifies it. Test exceptions thoroughly.

Phase 3: Accounting integration

Connect provider payment data to the accounting platform, using a clearing and reconciliation design approved by finance.

Phase 4: Collection integration

Stop reminders on confirmed payment, pause on payment claims, and surface unmatched receipts in the AR exception report.

Each phase should remove a measured bottleneck. Do not add a payment provider, integration, and custom collection workflow simultaneously unless the team can test and support the combined change.

The bottom line

PayNow invoice automation has three separate jobs:

  1. Make it easy for the customer to pay the correct entity
  2. Carry enough information to identify the invoice
  3. update and reconcile the accounting records safely

A QR code solves only the first job unless it is connected to a matching and reconciliation process.

Start with the simplest approach your invoice volume supports. Add dynamic references and provider integrations when manual matching becomes material, and keep uncertain payments in a human review queue.

For the wider invoicing workflow, read how to automate invoicing and payments for a Singapore small business.

Use the Calcudesk automation ROI calculator to estimate the time spent matching payments and chasing invoices. If your PayNow receipts cross several systems or create recurring exceptions, book a 30-minute discovery call and we will map the controls before recommending automation.

Back to journal Get my opportunity map