Somebody in the business decides to buy something, and by the time the bill arrives that decision is already old and nobody wrote it down. The procure to pay process is the name for the whole run, from the request to buy through to the supplier being paid. Most of the control in it sits in the first half, before any invoice exists. A firm that only inspects the second half is checking bills against orders it never placed.
What the Procure to Pay Process Covers, and Where It Stops
Procure to pay, shortened to P2P, is the end-to-end process that starts when someone asks to buy something and ends when the supplier has been paid and the transaction is on the books. It has two boundaries, and naming them is most of the value. The front boundary is the request. The back boundary is the payment.
Between them the run is short to name and hard to control. Somebody requests, somebody with the authority approves and the funds are reserved, an order goes out to the supplier, the goods or services arrive and someone records that they arrived, the invoice is set against the order and that record, and the payment is released.
Along that run the same purchase changes form several times, and federal payables practice names the stages it passes through. The Internal Revenue Manual calls them the purchasing chain, the four potential accounting stages for its own purchases: commitment, obligation, accounts payable and expense (IRS, Internal Revenue Manual 1.35.24, Establishing IRS Commitments and Obligations). Those rules bind a federal agency rather than your firm or your client, so what carries over is the sequence and not the duty.
The process on the other side of the ledger is record to report, which starts once transactions are on the books and runs through to the financial statements. Where the scope line falls inside that one, and which half of it can be handed to a provider at all, is set out in record to report services. Order to cash runs in the opposite direction, from a customer order through to cash collected, so it brings money in rather than committing it.
Source to Pay Is Wider, and the Two Are Not Synonyms
Source to pay takes in the work that happens before anyone decides to buy a specific thing. Microsoft's business process catalog breaks it into areas that begin with developing procurement and sourcing strategies, defining procurement catalogs and managing vendor relationships, then move on to procuring materials and services, processing vendor invoices, and issuing and settling vendor payments (Microsoft Learn, source to pay end-to-end overview).
Sourcing strategy, catalogs and supplier relationships all sit in that wider process, ahead of any particular purchase. Procure to pay is usually reserved for the narrower run that begins once a requirement already exists and a specific thing is being bought. Treating the two names as interchangeable quietly widens a scope conversation, because choosing and negotiating with suppliers is a different service from executing a buying cycle.
The Requisition Is Where the Money Is Committed
The first approval in the cycle is not the invoice approval. It happens at the requisition, meaning the internal request to buy something, and it happens while nothing is owed to anybody.
That step has three parts rather than one. A commitment is the reservation of a portion of budgeted funds signifying the future intent to purchase goods or services, and the commitment process is described as including the submission of the requirement, called the requisition, the validation and approval of the requirement, called the authorization, and the reservation of funds, called the commitment (IRS, Internal Revenue Manual 1.35.24, Establishing IRS Commitments and Obligations).
Read that as a design instruction. Asking, approving and reserving are separate acts, and a process that collapses them into one email has no point at which the money was visibly set aside.
Delegation of Authority Is a Written List With Dollar Limits on It
Who may approve a purchase, and up to what amount, is written down before anyone needs it. The federal rules are unusually blunt about this, and they are worth reading even though they bind agencies rather than firms.
A contracting officer, meaning the person authorized to enter into and sign contracts on the government's behalf, may bind the government only to the extent of the authority delegated, shall receive from the appointing authority clear instructions in writing regarding the limits of that authority, and information on those limits shall be readily available to the public and agency personnel (Federal Acquisition Regulation, 1.602-1, Authority).
The limit travels with the appointment rather than sitting in a policy nobody reads. Contracting officers are appointed in writing on an SF 1402, Certificate of Appointment, which shall state any limitations on the scope of authority to be exercised (Federal Acquisition Regulation, 1.603-3, Appointment).
Dollar level then decides which procedure runs at all. The lighter simplified acquisition procedures, meaning the shorter methods used for smaller buys, are prescribed for acquisitions whose aggregate amount does not exceed the simplified acquisition threshold (Federal Acquisition Regulation, 13.000, Scope of Part).
The micro-purchase threshold means $15,000, falling to $2,000 for construction covered by the federal wage rate requirements and $2,500 for services covered by the Service Contract Labor Standards, while the simplified acquisition threshold means $350,000. Both rise rather than fall for contingency and emergency work, the micro-purchase threshold to $25,000 inside the United States and the simplified acquisition threshold to $1 million (Federal Acquisition Regulation, 2.101, Definitions).
Below the smaller of those two, the authority is pushed outward rather than upward. Agency heads are encouraged to delegate micro-purchase authority to the individuals who will be using the supplies or services being purchased, appointed in writing under agency procedures rather than on the certificate (Federal Acquisition Regulation, 1.603-3, Appointment).
The shape underneath all of that transfers to a firm of any size. Authority is named, written, capped by amount, published to the people who have to obey it, and pushed down to the buyer for small routine spend so the approval queue is not carrying stationery.
Why This Approval Is Not the Invoice Approval
The two approvals answer different questions at different moments, and one cannot stand in for the other.
The requisition approval asks whether the firm should spend this money at all. It happens before a supplier has done anything, so refusing it costs a conversation. The invoice approval asks whether a bill matches the purchase that was already authorized. It happens after the supplier has performed and a liability exists, so refusing it is a dispute rather than a decision.
Everything downstream is a version of that second question. Two-way and three-way matching, price and quantity tolerances, and where the failed invoices queue up are all tests of a bill against documents that already exist, and they are worked through in invoice processing automation. None of them asks whether the purchase was a good idea, because by then that question has been settled by default.
The Purchase Order Is a Commitment Document
Issuing a purchase order is the act that turns an internal intention into an external one. It is not a form that follows a decision. It is the decision, put in a form the supplier can accept.
The federal definition makes the legal character explicit. A purchase order, when issued by the government, means an offer by the government to buy supplies or services, including construction and research and development, upon specified terms and conditions, using simplified acquisition procedures (Federal Acquisition Regulation, 2.101, Definitions).
An offer becomes binding when it is accepted. Where a binding contract is wanted before the contractor undertakes performance, the contracting officer shall require written acceptance of the purchase order by the contractor (Federal Acquisition Regulation, 13.302-3, Obtaining Contractor Acceptance and Modifying Purchase Orders).
What the document has to carry follows from that. A purchase order shall specify the quantity of supplies or scope of services ordered, contain a determinable date by which delivery or performance is required, and provide for inspection, with receiving reports accomplished immediately upon receipt and acceptance of supplies (Federal Acquisition Regulation, 13.302-1, General).
Then the accounting catches up with the commitment. An amount is recorded as an obligation only when supported by documentary evidence of a binding agreement that is authorized by law and prepared in writing, and an obligation is a definite commitment that creates a legal liability of the government for the payment of goods and services ordered or received (IRS, Internal Revenue Manual 1.35.24, Establishing IRS Commitments and Obligations).
That is why the order upstream is the precondition for every check downstream.
Vendor Onboarding Is the Front Gate, Not an Admin Step
The vendor record has to be complete before the first order goes out, not before the first payment goes out. Sequencing it the other way is how a firm ends up committed to a supplier it is not yet able to pay.
Federal practice puts the check at the quote rather than at the invoice. Unless the acquisition is exempt, the contracting officer shall verify that the offeror or quoter is registered in the System for Award Management, the federal government's central register of entities that want to do business with it, at the time an offer or quotation is submitted (Federal Acquisition Regulation, 4.1103, Procedures).
Registration is also more than one gate, and the separation is the part worth copying. Being registered means the offeror has entered all mandatory information including the unique entity identifier that names the business in the register and the electronic funds transfer indicator where applicable, that the offeror has completed the core, assertions, representations and certifications, and points of contact sections of the registration, that the government has validated all mandatory data fields including validation of the taxpayer identification number with the Internal Revenue Service, and that the record has been marked active (Federal Acquisition Regulation, 52.204-7, System for Award Management).
Banking identity and tax identity are separate fields with separate validations, and a clean answer on one says nothing about the other. A supplier can hold a valid taxpayer identification number and still have given you an account number that belongs to somebody else.
Getting the banking half wrong stops the payment, and it moves who carries the loss. Where the contractor's payment information on file is incorrect, the government need not make payment until correct information is entered, and any invoice is deemed not to be a proper invoice for the purpose of prompt payment (Federal Acquisition Regulation, 52.232-33, Payment by Electronic Funds Transfer).
The loss then follows whoever owned the wrong record. Where a transfer fails because the contractor's payment information was incorrect, or was revised within 30 days of the payment instruction being released, and the funds are no longer under the control of the payment office, the government is deemed to have made payment and the contractor is responsible for recovering the misdirected funds (Federal Acquisition Regulation, 52.232-33, Payment by Electronic Funds Transfer).
Three further duties attach to that same vendor record: who is allowed to edit the vendor master file, how a change of bank details is verified before it takes effect, and the Form W-9 and taxpayer identification work that decides next January's information returns. All three are worked through in what an accounts payable outsourcing case study has to report.
What the Cycle Looks Like With No Procurement Module
In a small firm, and in most of the client businesses a firm keeps books for, none of that P2P machinery exists. There is no requisition screen, no approval routing and no purchase order. Spend arrives as a bill somebody already agreed to, which makes invoices with no order behind them the normal case rather than the exception, and what that does to any automation project is set out in invoice processing automation.
Federal practice has a name for that pattern and a remedy for it. An unauthorized commitment means an agreement that is not binding solely because the representative who made it lacked the authority to enter into it, and ratification means the act of approving an unauthorized commitment by an official who has the authority to do so (Federal Acquisition Regulation, 1.602-3, Ratification of Unauthorized Commitments).
The conditions on that remedy are the useful part. Ratification may be exercised only where a list of conditions all hold, among them that the supplies or services have been provided and accepted or a benefit has otherwise been obtained, that the ratifying official holds the authority to enter into a contractual commitment, that the resulting contract would otherwise have been proper, that the price is determined to be fair and reasonable, and that funds are available and were available when the commitment was made (Federal Acquisition Regulation, 1.602-3, Ratification of Unauthorized Commitments).
Read as a firm-sized rule, that is a checklist for after-the-fact spend, not a permission to keep creating it.
The Workable Minimum for a Firm or a Client With No System
Five things get you a defensible cycle without buying anything, and each of them is a document rather than a feature.
One written list of who may commit money, and up to what amount. It fits on a page. Name people, not roles, and give each name a ceiling, with the route above that ceiling written next to it. The federal version publishes those limits deliberately, and the reason holds at any size, because a limit nobody can see is a limit nobody applies.
A floor under which no order document is needed. Set it where the paperwork stops being worth the money, then let the person who actually uses the thing buy it directly under that floor. Without a floor, either everything queues or nothing does.
An order document above that floor, however plain. An email that names the item, the quantity, the agreed price and a delivery date is an order document. It carries the things the federal rule asks a purchase order to specify, and it gives the eventual invoice something to be checked against.
Vendor setup before the first order, with the bank details confirmed apart from the tax form. Treat them as two completions rather than one, because they fail independently and only one of them is a payment risk.
A named person who ratifies or refuses spend that arrived without any of this. Somebody has to look at each after-the-fact purchase and decide whether to stand behind it. If that person is also the one who made the purchase, there is no control here at all.
Splitting authority, custody and accounting between different people is the control the whole cycle rests on, and it is worked through for payables in the same accounts payable case study.
There is an honest limit on all of this. Where one partner buys everything and signs everything, the written list is one line and the floor is high, and building more process than that is cost without a control. The test is whether more than one person can commit the firm's money, or whether the firm commits money on a client's behalf. A yes to either makes the list worth writing.
Writing the list is a morning's work. Doing the work behind it, on your own books and on every client set you keep, is where firms run out of people. Accountably places trained offshore accountants inside US CPA and EA firms, ramped on your software and SOPs in about 3 to 4 weeks, with the authorization and the payment release staying inside your firm. That is 20+ US firms and 30+ placements since 2022. Don't trust us. Test us. Put a block of your own work through the Free 40-Hour Proof Pilot and grade the output before a client file depends on it. If a placement is not the right fit in the first 30 days, we replace them free.
Start at the Front of the Cycle
The procure to pay process is easiest to inspect from the payment end and only fixable from the request end. Matching, tolerances and exception queues all assume a purchase order that somebody authorized before the money moved, and where that order was never raised there is nothing for any of them to do.
Take last month's payables and mark each invoice with the name of the person who agreed to the spend and the date they agreed to it. Every line you cannot fill in is a purchase your firm approved after it was already owed, and that list, rather than the invoice count, is the size of the problem.