Route NetSuite CAM exceptions
Give CAM exceptions their own state path. Do not bury them inside bill approval.
Start with a bill and source link. Then stop whenever needed proof is missing.
Oracle routes some PO gaps to pending approval. Its guide covers quantity and cost gaps.
That path does not test lease terms. A CAM review needs another evidence lane.
Start with one case record
Use the client bill as the start signal. Link a separate CAM case record to it.
The case record should hold:
- Bill ID
- Landlord vendor
- Entity
- Site
- Lease ID
- Statement year
- Source file links
- Current state
- Evidence ID
- Assigned owner
Do not overwrite the original bill fields. Keep the CAM case as a trace record.
No native CAMAudit record type exists. The consultant designs any custom record.
Use eight clear states
Give each state one plain meaning. Also name who can move it.
| State | Meaning | Move owner |
|---|---|---|
received |
The case record exists | System owner |
missing_files |
Required proof is absent | Client file owner |
lease_review |
Complete files await review | Firm reviewer |
partner_approved |
The firm signed the work | Firm lead |
disputed |
Counsel approved a sent dispute | Approved sender |
posting_approved |
The client approved an ERP step | Client approver |
closed |
Final evidence is attached | Case owner |
failed |
A system move did not finish | System owner |
The firm-approved state marks a role. Visible client copy can call it firm approved.
Do not use disputed for a draft.
Use it only after an approved notice was sent.
Guard every transition
Each move needs evidence and an approved owner. Do not rely on a date alone.
| Move | Needed evidence | Stop rule |
|---|---|---|
| Received to missing files | File checklist | No complete set |
| Received to lease review | Complete file set | Any required file absent |
| Lease review to firm approved | Signed review note | Open reviewer question |
| Firm approved to disputed | Counsel-approved notice | No send approval |
| Firm approved to posting approved | Client approval | No ERP authority |
| Any state to failed | Error log | Retry not complete |
| Any state to closed | Final proof | Open action remains |
Oracle work logs record starts and moves. They also trace actions and access failures. Oracle explains those logs here.
Keep similar trace data for custom work. Use only supported client features.
Define the missing file loop
Missing files should stop audit review. They should not close the case.
Store these fields in the loop:
- Missing file type
- Request owner
- Request date
- Source contact
- Last response
- Next check
- Escalation owner
Do not invent a lease value. Do not copy a guessed ERP field.
When the file arrives, validate its identity. Then return the same case to review.
Keep payment control separate
Oracle Bill Capture includes a payment hold feature. Oracle documents it for disputed bills.
That does not authorize your firm to use it. Client staff must own that choice.
Use a separate field for payment status. Do not make CAM state control payment.
The safe record should show both facts:
| Field | Example value |
|---|---|
| CAM case state | lease_review |
| Payment state | client_decision_needed |
| Payment owner | Client controller |
| CAM owner | Firm reviewer |
Do not advise a client to withhold payment. Route legal and payment choices to approved owners.
Preserve the evidence note
Every move needs a short decision note. The note should answer four questions.
- What source was checked?
- What did the reviewer identify?
- Who approved the move?
- What proof closes the next step?
Keep source line links beside the note. Keep the prior note after each update.
An editable text box alone is weak. Use author, time, state, and evidence fields.
Handle failed moves
Failed is a real work state. Do not hide it inside a system log.
A failed state should keep:
- Prior safe state
- Failed action
- Error text
- Acting role
- Retry count
- Next owner
- Resolution note
Oracle tells teams to check work logs. Those logs include failed actions and moves. The work log guide gives that process.
A retry must keep the same evidence ID. It should not skip an approval gate.
Walk one sample case
Maple Dental and these facts are fictional. Its facts show the proposed state path.
Maple Dental gets a landlord CAM bill.
The linked case starts at received.
The signed lease is missing. The case moves to the missing-file state.
The client adds the signed lease. The case then enters the lease-review state.
The reviewer flags one item. The firm lead checks and signs the work.
The case moves to the firm-approved state. It does not change the payment state.
Counsel reviews any dispute letter draft. Only an approved sender may send it.
The case closes after final proof arrives. The record keeps each prior state.
Copy the state worksheet
Use this sheet before custom build work.
| Field | Entry |
|---|---|
| Start record | |
| Source link | |
| Evidence ID | |
| Current state | |
| Move owner | |
| Approval proof | |
| Failure rule | |
| Retry owner | |
| Close proof |
The system guide maps the wider system.
The dimension guide governs shared keys.
The advisory guide sets the service boundary.
Return to the ERP consultant pillar for the full offer.
Use the Practice Growth hub to find other owners.
Browse nearby system work in the resource hub.
Where CAMAudit fits
ERP consultants can add this review to the NetSuite case.
The case record keeps the evidence ID. Link CAMAudit output to that ID.
CAMAudit reads only the files you supply. Those files include the lease and CAM bill.
Its fixed math checks may flag an item. The item can keep its source lines.
Your firm reviews and signs the branded CAM audit. The case owner can attach that approved work.
CAMAudit may prepare a dispute letter draft too. The firm reviewer checks it first.
It is not legal advice. Have counsel review before sending.
Client staff keep payment and posting control. CAMAudit has no turnkey NetSuite connector.
Set each case owner with the service line guide.
Ready to add this work to your firm? Get started.
Sources
- Oracle vendor bill approval, current help
- Oracle flow issue help, current page
- Oracle Bill Capture, current help
- Oracle vendor bill exception criteria, current help