In short
AP portal invoicing and collections covers two kinds of customer. Enterprise buyers on Coupa or SAP Ariba need each invoice filed in their portal, which Monto automates. Everyone else gets an emailed invoice that someone has to chase and make easy to pay, which Finero automates, along with posting every payment back to your ERP.
Key takeaways
- A portal covers only part of the book, and approval is not payment: Coupa and SAP Ariba both tell suppliers to contact the customer about when they will be paid.
- Monto files and tracks invoices in AP portals. Finero chases every other customer with a card and ACH payment link, handles replies and disputes, and posts the cash.
- They run side by side with no direct integration: each connects to your ERP, which stays the single record both work from.
Most B2B suppliers do not have one kind of customer. The large enterprise accounts insist on their own procurement system, and an invoice that is not filed there does not exist as far as their AP team is concerned. The rest of the customer list still receives an invoice by email and pays when someone reminds them.
A process built for one group leaves the other uncovered.
What does AP portal invoicing and collections involve?
Two jobs that sound alike and are not. Portal invoicing is getting the invoice accepted inside the customer’s system: the right format, the right purchase order, the fields that buyer requires. Collections is getting the money: reminding, answering questions, resolving disputes and recording the payment when it lands.
For a portal customer you need both, in order. For an email customer you only need the second, but you need it for every invoice, every week. The question to ask about any tool is which of those jobs it does and for which customers.
Which customers need a portal, and which need chasing?
Sort the customer list by how each one pays. The split decides the tooling.
| Customers on an AP portal | Customers paid by email invoice | |
|---|---|---|
| How the invoice arrives | Filed in Coupa, SAP Ariba or the buyer's own portal | Emailed as a PDF or a link |
| What blocks payment | A rejected or never-filed invoice, a PO mismatch, a dispute in the portal | Nobody followed up, or paying takes effort |
| What gets it paid | Correct submission, then follow-up with AP after approval | Reminders before and after the due date, and an easy way to pay |
| Who covers it | Monto files and tracks; Finero follows up | Finero, end to end |
If every customer were on a portal, portal automation plus a person following up would be enough. If none were, a collections tool alone would do. Most suppliers selling to enterprises have both groups, and that is where two tools that each do one job well cover more ground than one tool stretched across both.
What happens after a portal approves an invoice?
Approval feels like the finish line. It is not. In Coupa, an approved invoice is one accepted for payment by the customer, and the Coupa supplier FAQ says it is then paid on the payment terms you set with that customer. For payment questions, Coupa’s advice is to contact the customer directly.
SAP Business Network says the same thing more bluntly. If an invoice does not move past Approved, you need to contact your customer to find out when to expect payment, and it is the customer’s responsibility to tell you when you will be paid. The payment itself goes from the buyer to you, not through the network.
Coupa and SAP Ariba invoice statuses, and whose move each one is
| Status | What it means | Whose move |
|---|---|---|
| Coupa: Pending Approval | Under review by the customer | The customer's approvers |
| Coupa: Approved | Accepted for payment; paid on the agreed terms | The customer's AP; you follow up |
| Coupa: Processing | With the AP department and should be paid soon | The customer's AP |
| Coupa: Disputed or Voided | The customer disagrees or something is wrong | You: correct, credit or resubmit |
| Ariba: Sent | Received but not yet approved or rejected | The customer; ask if it stays there |
| Ariba: Approved | Approved for payment | You: contact the customer for a date |
| Ariba: Paid | Paid, or payment is being issued | You: match the cash |
| Ariba: Rejected | Failed network validation, or the customer rejected it | You: fix and resubmit |
Statuses can vary by buyer, because each customer configures its own portal. Check the notes on the invoice before acting on one.
Where portal invoices stall
- Before approval: a rejected invoice, a missing or mismatched PO, or a Coupa tolerance hold when the amount differs from the PO by more than the customer allows.
- After approval: the invoice waits for the buyer’s payment run, and nobody on your side asks when that is.
- After payment: the cash arrives without remittance. SAP notes that not every customer sends remittance information to the network, so someone has to match the payment to the invoice.
A rejected or mismatched invoice is a filing problem. Waiting on the payment run and matching cash without remittance are collections problems, and they belong to whoever runs collections for the rest of your customers.
What the gap costs finance
For a CFO, approved but unpaid portal invoices are the most frustrating part of DSO. The work is delivered, the customer has accepted the invoice, and the cash is still not in the bank. Every week it waits is working capital tied up for no reason anyone can name.
The email customers carry the opposite risk. Without follow-up, invoices drift past due, some become write-offs, and the usual fix is to hire another collector. That spend grows with the customer list, while the cash flow problem it was meant to solve stays the same shape. Covering both groups with software is the business case: DSO falls on the portal accounts and the email accounts together, without adding headcount.
Who covers which stage: Monto and Finero
Monto is built for the portal half. Its product page describes connecting to more than 500 AP platforms, checking each invoice against the destination’s requirements, matching it to the purchase order, tracking its status and retrieving payment details from the portal. Most invoices land within an hour, with a 24-hour commitment. Finero is built for the collections half, across every customer.
| Stage | Monto | Finero |
|---|---|---|
| File the invoice in the customer's portal | Yes, across 500+ AP platforms | - |
| Check it against the portal's rules and the PO | Yes | - |
| Track portal and PO status | Yes | - |
| Chase customers who are not on a portal | - | Yes: email on Core; email, SMS and chat on Scale |
| Give the customer a way to pay | Payment happens in the buyer's process | Card and ACH link on every invoice |
| Answer replies and route disputes | - | Yes, with the invoice attached |
| Follow up on approved but unpaid portal invoices | Retrieves payment details from the portal | Yes, within the policy you set |
| Post payments back to the ERP | Confirms payments and remittance from the portal | Yes; automatic reconciliation on Scale |
The overlap is small and sits at the end, where both touch the payment. Monto reports what the portal says about it; Finero records it in the ERP and chases whatever is still open.
How to run both without chasing a customer twice
- Split the customer list. Mark the accounts that require a portal. Those go to Monto for filing.
- Connect both to the ERP. Monto offers a NetSuite bundle and connections to other ERPs; Finero connects to QuickBooks Online and Xero on Core, and NetSuite, SAP, Oracle Fusion and Dynamics 365 on Scale.
- Set Finero’s policy for portal accounts. Require sign-off before any contact on those accounts, so nothing reaches a portal customer’s AP team that your team did not approve.
- Let Fin run the email customers. Reminders before and after the due date, a payment link on every invoice, replies answered and disputes routed with the invoice attached.
- Follow up on approved portal invoices. When a portal invoice passes its terms unpaid, the follow-up goes out under the same policy.
- Post every payment once. Payments are written back to the ERP, and Monto’s portal payment details help match the ones that arrive without remittance.
When you need only one of them
If almost every customer pays through a portal, start with portal automation and judge whether the follow-up after approval is big enough to automate. If none of your customers use portals, a collections platform covers the whole cycle on its own. If you are weighing Monto against other tools rather than alongside one, the Monto alternatives comparison sets out the options.
Monto does not publish its pricing. Finero Core is $399 a month, billed monthly, with 200 successfully paid invoices included and a 30-day free trial; Scale is priced for higher volume and enterprise ERPs. See pricing, and what Fin, the AI collections agent, does.