Esc

↑↓ move↵ openIndex · Pagefind
Accounting apps / Work in Progress (WIP)

Work in Progress (WIP)

ASC 606 percent-complete WIP: compute, approve and post over- and under-billings and loss provisions from posted cost and billings.

On this page

Work in Progress computes the WIP schedule for an entity at a period end from posted job cost, posted billings and frozen forecasts. Each snapshot is a revision that is reviewed, approved by someone else and posted as an auto-reversing entry. Open it from the company app launcher under Accounting > Work in Progress (WIP); it appears when your accounting access includes it.

Who uses it
Controllers and accountants compute and post; a different approver signs off.
When
Each month end, after forecasts are approved.
What it holds
Revisioned snapshots with one row per job, exceptions, overrides with reasons, attachments and the posting entry.

Key workflow

  1. Compute the snapshot. Contract value is the executed prime schedule of values plus approved prime change orders. Cost is posted job cost, billed is posted AR, and the estimate at completion is the forecast frozen at the period end. Percent complete is cost-to-cost unless the job is set to as-invoiced.
  2. Review the rows. Each row shows earned revenue, over- or under-billing, retainage receivable (as a contract asset when conditional), pending change orders as a memo column and job cash position. Jobs whose inputs fail are exceptions that block approval.
  3. Override with a reason. Pending change orders enter the transaction price only through an explicit override, which is recorded with its reason.
  4. Approve. A different person approves. Exceptions need a written acknowledgment; a failed computation cannot be acknowledged.
  5. Post. Posting writes the over/under-billing and loss provision entry on the WIP journal at the period end, reversing on the first day of the next period. A later revision supersedes the earlier posting.

Controls

  • If job cost, billings or forecast inputs change while a snapshot computes, the snapshot is refused rather than saved stale.
  • The preparer cannot approve, and approval and posting are idempotent per snapshot revision.
  • The WIP-to-GL reconciliation report compares the posted schedule with the ledger for close review.

Current boundaries

For the full procedure, exceptions and examples, read the Job cost and WIP workflow guide.

API operations

8 operations · 3 read · 5 write · base path /rest/v1.0/companies/{company_id}/accounting

  1. GET /jobcost/wipList WIP snapshots (newest period end and revision first), 100 per page, filtered by entity, period and status.
  2. POST /jobcost/wipCompute the next WIP revision for an entity at an ended period (postJournal and viewLedger). Contract = executed prime SOV + approved prime COs; cost = posted job cost; billed = posted AR; EAC = the forecast frozen at the period end (PM approval or soft close) plus job cost posted since the freeze beyond what the freeze already held on each cost code (only cost on a commitment-linked line consumes the open commitment frozen there; a budget_remaining code rises to max(frozen EAC, actual + commitment left)), else the approved live forecast, unless overridden with a reason. Each job uses its revenue method (cost_to_cost or as_invoiced); pending prime COs are the memo column (pendingChangeOrders) and enter the transaction price only through overrides[].change_orders; retainage receivable comes from AR (retainageContractAsset when the job's retainage is conditional); each row records settings.loss_provision_unit; cash position is AR receipts less AP payments on the job (payroll and other direct cash costs are not included). A job whose inputs fail is a compute_failed exception, and an executed contract with no value against a positive EAC a contract_value_missing exception (not on completed_contract jobs; the other jobs still compute); both block approval. Rows are read without the company posting lock; the insert refuses with 409 if job cost or billings were posted, or job forecast inputs changed, meanwhile. Supports Idempotency-Key.
  3. GET /jobcost/wip/{id}Get a WIP snapshot with its job rows; format=csv returns the rows as CSV
  4. POST /jobcost/wip/{id}/approveApprove a draft snapshot (approveJournal; the preparer cannot approve). A snapshot with exceptions needs exceptions_note; compute_failed exceptions cannot be acknowledged. Idempotent; a rejected snapshot is refused.
  5. GET /jobcost/wip/{id}/attachmentsList attachments on a WIP snapshot
  6. POST /jobcost/wip/{id}/attachmentsAttach a file to a WIP snapshot
  7. POST /jobcost/wip/{id}/postPost an approved snapshot on journal WIP at the period end with autoReverseDate the next day; idempotent on (snapshot, revision). Supersedes an earlier posted revision for the period.
  8. POST /jobcost/wip/{id}/rejectReject a draft or approved snapshot (approveJournal; terminal, compute a new revision), or with return_to_draft send an approved one back to draft (approval and acknowledgment cleared). Audited with the reason.

Parameters, request and response fields, errors and a generated example for each operation are in the REST reference for this app. Read scopes, step-up and permissions in the Accounting API guide.

Keep exploring

Related across os.construction

Run it on your own project.

Start a 14-day free trial. Want a say in what ships next? Join the founding program.

Your role (optional)

14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →

Ask the OS

Reading this page

Ask anything about this page. Answers use what you're reading as context.

Suggested

    AI · may be imperfect · sample data where shown

    Open file