An accounting lead at a real estate developer mid NetSuite go-live described the old loop without exaggeration. Print the invoice. Walk it around the office for approvals. Scan it back in. Capture manually. Somewhere in the same confession: storing invoices in cardboard boxes for a year of coping.
They were not shopping for a romantic story about paperless offices. They wanted automation that would let approvers act without buying every person a NetSuite seat, and extraction rules strong enough that capture stopped being re-key theatre.
The direct answer: digital approvals and instructable extraction make the print-walk-scan-key loop optional. Cardboard boxes were never a retention strategy. They were a symptom.
This matters most if you are leaving a paper approval culture during an ERP go-live, if seat cost is shaping who can approve, and if boxes or shared drives are still the archive.
The loop has four failure points
Print introduces version drift. Walk introduces delay and lost paper. Scan introduces image quality problems. Key introduces human error. Each step feels cheap. Together they are an AP system made of shoes and toner.
The loop tends to survive the moment a company buys NetSuite, or any ERP, because approvers are not all licensed. The ERP becomes the ledger. The hallway remains the workflow.
Real estate and home building make the cardboard vivid, but the loop shows up in wholesale and manufacturing too. The artifact changes. The shoes stay.
Benchmarks and retention reality
Ardent Partners' Metrics That Matter in 2025: $9.40 average cost per invoice, 32.6 percent touchless, 14 percent exceptions. Paper-heavy approval chains are a structural way to stay on the wrong side of those averages.
CRA guidance expects businesses to keep records for six years from the end of the relevant tax year in normal cases. Boxes can store paper while failing retrieval. Digital archives only win if they remain complete and readable. "Optional cardboard" is not "delete everything."
Hallway-to-digital diagnostic
Removing the print, walk, scan and key loop
Finofo takes the invoice in digitally, by email, upload, photo or shared folder, so there is nothing to print and nothing to scan. Extraction rules on the vendor encode how to read messy documents, so repeat vendors stop being re-keyed. Approvers get a personalised inbox with mobile approval and biometric login, without a NetSuite seat, so the walk becomes a notification. The bill lives on one AP object with its approval trail and its PDF, retrievable by vendor, date, job or PO, which is the retention strategy the boxes were pretending to be. For the developer, occasional approvers across ten subsidiaries approve from their phones, the org switcher keeps each entity’s books separate, and the verified bill posts to NetSuite with the approval attached.
We rejected the idea that ERP go-live alone retires hallway approvals. Ledgers do not walk themselves.
The loop dies because the whole flow is one engine. Finofo runs accounts payable, expense management and purchasing on one AI native platform, built in Calgary for Canadian finance teams, so the same digital path handles a vendor invoice, a site manager’s texted receipt and a PO raised for a subcontractor. One inbox for approvers, one archive, one posting path into NetSuite per entity.
What stays with your team
Some parts of this process belong with the finance team, by design. Finofo is built to keep them there.
Retiring paper is the easy half, and plenty of tools do it. What makes it worth doing is what runs underneath: extraction depth that makes the approved PDF trustworthy, and multi entity sessions that make ten subsidiaries workable. Finofo pairs the digital approval with both, which is why the hallway stays dead after the novelty wears off.
Bills that live on a vendor portal are an intake decision your team makes. Finofo handles every document that reaches it by email, upload or folder; where a utility or carrier only offers a portal download, the step of retrieving it is a process your team owns, and the retrieved PDF then takes the same digital path as everything else.
Seat strategy is a finance decision that Finofo removes from the approval path. Occasional approvers act in Finofo without an ERP licence, so the question of who gets a NetSuite seat becomes an accounting question rather than a workflow constraint.
Back to the hallway
Print, walk, scan, key felt responsible. It was mostly slow. Put the bill in a system people can approve without shoes. Keep records for CRA. Leave the boxes for moving day.
Seat cost is an AP design input
Finance teams sometimes treat licensing as procurement's problem and hallway routing as AP's problem. They are the same problem. If occasional approvers cannot act without a full ERP seat, paper returns. Score automation options on whether approval can happen without seat sprawl, not only on whether the ERP can store a PDF.
What to film in week one of an ERP go-live
Film one invoice that used to print. Show intake, extraction rule if relevant, approval by someone who does not have a full ERP seat, and retrieval of the stored PDF. That forty-second clip beats a paperless slogan in any steering committee. If you cannot film retrieval, you have built another box, just with electricity.
Multi-entity developers feel the hallway twice
With roughly ten NetSuite entities live and a hundred to two hundred invoices a month, hallway approvals multiply by entity politics. Digital approvals plus an org switcher are paired needs. Ending cardboard without ending session thrash leaves half the pain. Treat them as one modernization story.
Extraction is what makes digital approvals honest
Digital approval of a bad keying job just moves the hallway error into software. Extraction rules that pull PO numbers, pick tickets, and quantity-shipped columns correctly are what make the approved PDF trustworthy. Pair the cardboard story with extraction depth or you will digitize a mess.
Boxes fail retrieval under time pressure
The painful audit moment is never "do we have boxes." It is "find the invoice for this vendor on this job from March." Cardboard fails that test. Shared drives without structure fail it too. Digital AP objects win when search fields are mandatory and attachments cannot wander into personal folders. Build that discipline during go-live week, not after the first CRA request.
Steer clear of paperless vanity metrics
"Percent paperless" is a weak KPI if retrieval still fails and coding is wrong. Prefer: median hours from invoice receipt to approval, share of invoices that never print, search success in under a minute, and correcting journals after post. Those numbers describe whether the hallway actually died.
Approver UX without app theatre
Occasional approvers will ignore a heavyweight app. They will respond to a clear queue and a short action. Design approval for the person who approves twice a week, not only for the AP clerk who lives in the system. That design is what kills the walk around the office.
Paperless is the opener. The engine underneath is the product.
This hallway story is where most teams start, and it is a real win. The lasting difference is what the digital bill carries with it: extraction rules that read the vendor's document properly, sessions that let a controller work several entities at once, and approvals that never require a seat. Evaluate on those, and paperless takes care of itself.
Go-live week is the best window
Wait six months after ERP go-live and hallway habits harden. Pair AP automation with subsidiary go-live while training attention is already allocated. The cardboard boxes disappear faster when the ledger change and the workflow change arrive together.
If this is your process
If invoices still print for signatures during or after an ERP go-live, or if cardboard or personal folders are the archive, this post is your checklist. If you are already fully digital and searching is instant, skim for seat-sprawl and extraction pairing, then move to deeper topics .
Frequently asked questions
Do we need mobile approvals on day one?
Ending print and walk is the day one win, and mobile is how it sticks for approvers who are rarely at a desk. Finofo includes mobile approval with biometric login, so the two arrive together.
Will NetSuite seats go to zero?
Unlikely, and that is not the goal. The goal is that every occasional approver does not need a full seat to unstick AP. In Finofo, approvers act without an ERP licence and the verified bill posts to NetSuite once.
