Questions

Click Start now, then use Proto to configure Procurement for your business. Set up your workflows, import your data and invite your team.

Procurement covers requests, sourcing, orders, amendments and receipts. The configured connection sends the approved order and receipt evidence to accounts payable, which owns invoice matching, adjudication and payment. Returned mismatches become work for the Buyer to resolve.

Rules use department, cost center, category, amount and tier to identify an eligible person. Department heads and budget owners come from maintained records; executive and committee tiers need explicit assignments. Submitted content is frozen, and the approval retains the policy and document scope reviewed. A change that exceeds that authority requires another decision.

An eligible order can use a prior spend approval within its remaining amount and scope. Conversion does not erase that authority, and splitting a request does not multiply it. An RFQ award alone grants no approval to spend. Eligible hand-raised orders may use the configured Buyer limit; other orders and exceptions follow their required review.

A Receiving Clerk can record dock receipts at locations without warehouse management. Requesters confirm eligible desk receipts for their own purchases. At managed locations, the warehouse connection supplies the agreed receipt evidence. Partial deliveries keep the remaining quantity visible, and a shipment notice alone does not prove receipt.

Use an amendment with a reason, the proposed revised order and the required approval. Review considers cumulative increases and the remaining agreement capacity, so repeated small changes cannot create unlimited additional commitment. The applied revision is retained for supplier acknowledgment and the finance connection.

Suspension prevents new or increased commitments while allowing authorized fulfillment of previously issued orders. A block holds issue and fulfillment posting until the designated review resolves it; arrivals can still be recorded for quarantine or dispute. Controlled reductions, cancellations and returns retain their evidence. Configure and rehearse these paths before launch.

Departments, policy complexity, supplier data, open orders and the finance and receiving connections determine the work. Agree the first launch scope after reviewing those inputs, then proceed when its rehearsal and migration reconciliation pass. Proto can prepare later changes for review; its model and machine usage are metered.

Access follows the role and record. Requester and Viewer roles cannot see protected contract prices or quoted totals. Approvers receive the information permitted for their assigned decisions without access to restricted contract-rate fields. An agent has the same access boundary as its configured role.

The Buyer collects responses against the same RFQ scope and compares the configured price, lead-time and quality measures. The quality input is based on accepted performance history; delivery performance is reported separately. The Buyer records the award reason, and the resulting order must still have valid spending authority.

During implementation, configure portal or EDI participation with each supplier. Supplier access is limited to its own permitted invitations, responses, orders and supporting records. Acknowledgments identify the order revision; qualification evidence waits for the assigned internal review.

There is no per-user fee for ordinary manual work. Prepaid credits cover metered operations, with model and Proto charges described separately. Implementation is priced to the agreed scope. The pricing page contains the full rates and account terms.