Purchase orders with approval
From request to close, with receiving by line, own numbering and PDF. With the approval policy from Automations, an order above a given amount needs approval before moving on; it can have one level or several.
Remotjob runs the whole buying cycle: suppliers, purchase orders with approval and receiving, supplier invoices, payments applied to the oldest invoices and a running account per supplier with its debt aging. It is the buying mirror of your sales, in the same place.
Buying tends to be scattered across emails with the order, a PDF of the invoice, a payment spreadsheet and the memory of whoever knows how much each supplier is owed. Procurement and payments joins that chain: the order is created, approved, received, invoiced and paid, and each supplier’s debt updates by itself.
Each step leaves its own record and numbering, so nobody has to reconstruct what happened.
Each supplier stores its tax ID, contact, currency, payment term, credit limit, default expense category, bank details and the alias under which it appears on the bank statement.
The order carries lines with an optional product, quantity, price, tax and expense category, and moves from request to approved, sent, partially or fully received and closed. It has its own numbering per organization and a PDF. If you enable an approval policy, an order above a given amount cannot be approved without going through the right people.
You receive by line and the order status moves on its own: partially received or fully received.
You can generate the supplier invoice from the order or enter it by hand, under the United States or Chile document regime. The due date defaults to the date plus the supplier’s payment term, and credit notes reduce the debt.
You record the payment with its method, account and reference, and apply it by hand or let it go automatically to the oldest invoices first. What is not applied stays as an advance. The paid amount of each invoice is calculated by the system; nobody types it in.
The running account shows each supplier’s balance with its debt aging (current, 1-30, 31-60, 61-90 and over 90 days) and a statement with running balance you can download as CSV or PDF.
From request to close, with receiving by line, own numbering and PDF. With the approval policy from Automations, an order above a given amount needs approval before moving on; it can have one level or several.
Generated from the order or entered, under two document regimes (United States and Chile). Credit notes reduce the debt and an invoice subject to a policy stays in draft until approved.
Manual or automatic allocation to the oldest invoices first. A payment cannot allocate more than its amount or more than the invoice balance, and voiding a payment recalculates its invoices.
Balance and debt aging per supplier, and a statement with running balance downloadable as CSV or PDF.
Documented spend by category, contrasted with actual spend from the connected bank: the difference is spend with no supporting document.
If your organization has a connected bank, outgoing transactions with no payment attached appear with a suggested supplier, and one click turns them into a payment and applies it. When you register it, the supplier learns its bank alias.
The invoices Remotjob issues to you show up in your purchasing module as what they are for you: a purchase from your supplier. With period, totals, detail and PDF download, read-only.
If your supplier also uses Remotjob, you see the catalog it shares with you at your price and create the order as a draft; the approved order can be sent through the network and arrives at the supplier as an order, and its invoice comes back as a draft.
The module ships with its map: what your team does, what the system does and what a person decides at each step.
This is where the organization’s money is committed. Every step has its record, its permission and its rules, and what is paid is never typed in by hand.
Suppliers, purchase orders with approval and receiving, supplier invoices, payments with allocation, a running account with debt aging, spend control and reconciliation with the connected bank. It is the buying side of the platform, just as Sales and collections is the selling side.
You can apply it by hand or let it apply automatically, starting with the invoices due soonest. Whatever is left stays as an advance. The paid amount of each invoice is calculated by the system.
Yes. With a policy in Automations, purchase orders and supplier invoices above a given amount need approval before moving on; the policy can have one or several levels, also staged by amount.
You see them in the Remotjob invoices tab of the same module, as purchases from your supplier: with period, totals, line detail and PDF download.
If your organization has a connected bank, outgoing transactions with no payment attached are suggested with their supplier and turned into a payment with one click. Without a connected bank, you record payments by hand.
Tell us how you buy and pay today: we will walk you through a purchase order from creation to payment in Remotjob.
Solutions companies usually run alongside this one, on the same workflow.