The staffing back-office checklist

Why the back office decides your margin

A staffing placement looks simple on a whiteboard: a client, a consultant, a bill rate, a pay rate. In practice, the space between those four facts is where agencies bleed. A COI that never got forwarded stalls a start date. A timesheet approved by the wrong person becomes a dispute. Hours that never reconcile against the rates you actually agreed become margin you quoted but never collected. None of these are recruiting problems — they are record-keeping problems, and they compound.

The fix is not working harder at email. It is a checklist where every item produces a record — who did it, when, and against which client, consultant, and rate. Run this list per placement and the end-of-month scramble mostly disappears.

Before the placement starts

• One record per relationship, with a role. Is this company your end client, a vendor between you and the client, or a supplier providing the consultant? The role changes who you invoice and who you pay — keep it explicit and deduplicated, not implied by whoever last touched the spreadsheet.
• One record per person, with an engagement type. W-2, 1099, or C2C changes your payroll, tax, and insurance obligations. Record it when you record the person. If consultants will submit their own hours, capture an email up front so their portal invite is claimable.
• Bill and pay rates locked together. Record both rates at the same moment, on the placement itself, and refuse a placement where pay exceeds bill. Margin should be a known number before the first hour is worked, not a discovery at invoicing time.
• Certificate of insurance in hand — validated, not just received. Most client MSAs require proof of coverage before work starts. Request it with structured limits (coverage line, per-occurrence, aggregate) so a shortfall is caught by comparison, not by a lawsuit.
• Work authorization status recorded. For H-1B, OPT, PERM, or green-card matters, track the case status and who is handling it — your team or an outside firm — so a filing deadline never surfaces as a surprise.

While the placement runs

• Timesheets on a fixed cadence. Period start, period end, hours. Submitted by the consultant or recorded by your team — but always against a named person.
• Approval as an explicit, logged act. Approving hours is the act that authorizes pay. It should be done by someone with that specific authority, and it should leave a log entry — not a thumbs-up in a chat thread.
• Every approved timesheet linked to its placement. Hours without a placement have no rates; rates are what turn hours into a receivable, a payable, and a margin. Link before you bill, every time.
• Settlement posted, not calculated ad hoc. When approved hours meet a placement's rates, post three amounts to a ledger: what the client owes you, what you owe the worker, and the margin between them. Post it once, keep it immutable, and correct mistakes with a reversing entry that names its reason — never by editing history.

Always on, in the background

• Documents with versions. COIs, agreements, and filings change. Keep the current version resolvable and the history intact.
• Separation of duties. The person who can approve hours is not automatically the person who can move money. Grant capabilities role by role, and let the system — not habit — enforce who can do what.
• An audit trail you would show an auditor. Every consequential action should append to a tamper-evident log. If your system of record is a spreadsheet, your audit trail is “trust me.”

How PoPayOne runs this checklist

PoPayOne wires each item above as a workflow, not a reminder. Gyani, the AI Chief of Staff, sets up clients, consultants, and placements from a two-minute conversation. Placements require bill and pay rates together and reject negative margin. COI requests carry structured limits and are auto-checked conservatively — anything the check cannot positively confirm goes to human review rather than silently passing. Timesheets flow submit → approve → link → settle, and settlement posts receivable, payable, and margin to a double-entry, append-only ledger.