Summary

  • Finofo’s September 9 launch extends its accounts-payable platform to expenses and purchasing without requiring customers to replace their corporate cards.
  • The documented expense workflow uses transaction data; purchasing can seek approval before a purchase order is issued. One policy model does not make those two moments identical.

A card charge waiting for its receipt and a purchase request waiting for permission may reach the same finance team, but they ask different questions. The charge needs to be explained and recorded; the request may still be stopped before a commitment is made. Finofo’s September 9 launch of expense management and purchasing puts both inside an expanded accounts-payable workflow. Its commercial pitch is that customers can keep the cards, banks and accounting systems they already use.

That is a narrower—and more useful—proposition than replacing an entire spending system. The Calgary-built company says it does not issue cards or make a new corporate-card programme a condition of using the software. Retaining an existing card removes one potential migration requirement. It does not, on the evidence provided, establish universal bank connectivity or control over a card issuer’s transaction-authorisation decision.

A charge needs data before it can be reconciled

Finofo’s expense product description specifies two ways to obtain statement data: a connection to the bank or card provider, or an upload when a direct connection is not used. Receipts may arrive by text, email, upload or mobile. Matching draws on merchant, amount, currency and date. The company says strong matches can link automatically, suggested matches need confirmation, and unmatched charges remain visible pending resolution.

The alternative upload route matters. “Keep the card” should not be read as “every card has an immediate feed”. A finance team still needs to know which source supplies the transactions and when that source is complete. A receipt without the corresponding statement entry, or a charge without its receipt, remains a different operational state from a finished accounting record.

Nor does the detailed product account remove people from the process. It describes team approval and finance review, including accounting codes and supporting evidence, and says users do not approve their own expenses. The launch release’s broad automation language should be read alongside those explicit review steps. Corporate-card reconciliation also differs from reimbursing an employee: approved personal or out-of-pocket claims become payables, which can be paid through Finofo or recorded as paid externally.

Purchasing can move the decision earlier

The purchasing module has a different starting point. A spend request can be routed for approval before a purchase order is issued. Teams may create POs within Finofo or bring them in from an existing system. Receiving records capture goods or accepted services, including partial receipts; invoice matching then checks what was approved and received against the supplier’s bill.

That sequence gives approval a prospective role. Yet the company expressly allows businesses to choose where a procurement process is needed rather than requiring a PO for every purchase. Missing orders, price differences or receiving gaps can be sent for further review, with tolerance rules set by the customer. The coverage of those rules is therefore part of the implementation, not something implied by a shared inbox.

Finofo says invoice approval policies can extend to expenses and purchasing without being rebuilt. Reusing rules for amount, entity or department may simplify administration. It does not turn review of a recorded card charge into the same event as permission to raise an order. The distinction is important when buyers describe what their controls actually prevent, and what they document afterwards.

The integration offering adds another boundary. Finofo says intake and matching can begin before ERP integration is complete, with coded invoices posted back when ready. It lists prebuilt accounting connections and support for custom workflows. Those are supplier descriptions, not proof that every customer configuration requires no implementation work or has a particular synchronisation guarantee.

The launch broadens the choice for finance teams that want new software without a new card programme. Its value will depend on transaction coverage, exception handling and the handoff into accounting. Keeping familiar payment instruments may ease adoption; establishing which decision happens at which stage is what makes the resulting workflow intelligible.