Amplify Audit: Default Prompts

For this Placement, I want to run an audit and check for the following
items. For a Placement to pass audit, all of the following must be true.
Please evaluate all of the following conditions.
 
Each check produces a ✅ pass or ❌ fail result with reasoning.
 
**Assignment Fields**
1.  Date Validity -- Scheduled End must not be before Start Date.
2.  Bill Rate Match -- Bill Rate on the assignment must match the REG
    bill rate on the rate card.
3.  Business Line -- Business Line must be selected and not blank.
4.  OT Type by Worker Class -- EmployeeOTType must be "No OT Calculated"
    for 1099 workers and "Default OT Rules" for W2 workers.
5.  Billing Profile Status -- Billing Profile must not read "Needs Review".
6.  Pay Group -- Pay Group must be populated.
7.  Exemption Status -- Exemption Status must be populated.
8.  Workers Comp Code -- Workers Comp Code must be populated for all W2
    workers.
9.  Expense Indicator -- Expense Indicator must be ON if expense earn codes
    are present on the rate card; OFF if none are present.
10. Sales Tax Group -- If placement state is CT, NM, WA, or WV, the Tax
    Group on the work location must contain data.
11. Work Location Name -- Work Location Name must not exceed character
    limits or contain special characters that would prevent BTE sync.
 
**Pay Bill Details**
12. Per Diem Ruleset -- Per Diem Ruleset must be selected if any stipend or
    per diem earn codes are on the rate card.
13. Daily Rate + Per Diem -- If a Daily Rate earn code is on the rate card,
    a Per Diem Ruleset must also be selected.
14. Cost Center -- Cost Center must be populated if required by the Client
    Engagement.
 
**Pay & Bill Rules**
15. Rules Configured -- Pay and Bill rules must be configured on the
    placement.
16. PA Taxable Margin -- If placement is in Pennsylvania with sales tax, the
    Taxable Margin field must be populated on all rate card earn codes.
 
**Time & Expense Setup**
17. Approval Method -- Approval Method must be Email/Electronic Approval
    with a time approver populated, unless Time and Expense Source is VMS
    Provider.
18. Time and Labor Enabled Date -- Time and Labor Enabled Date must be on
    or before Start Date.
19. T&E Source Match -- Time and Expense Source must match the Client
    Engagement setting for the relevant business line.
20. Approval Method -- Approval Method must match the Client Engagement
    for the business line.
21. Timecard Approver Populated -- Timecard Approver must be populated when
    Time and Expense Source = Web AND Approval Method = Client Web Approval.
22. Timecard Approver Format -- Timecard Approver must not exceed character
    limits or contain special characters that prevent BTE sync.
 
**Accounting & GL**
23. Accounting Class -- Accounting Class must be valid and map to an active
    GL code.
 
**Compliance & HR**
24. Required Documents -- Required compliance documents must be present in
    the placement folder.
25. Background & Drug Test -- Background Check and Drug Test must be
    completed where required.
26. CRFs Present -- All expected Customer Required Fields must be present.
    Use the CRF labels configured for your firm.
27. Shift Assignment -- If shifts exist at the company level, a Shift must
    be assigned to the placement.
 
**Worksite & Location**
28. Tax State Consistency -- Tax State on the Candidate record must match
    the Placement Worksite Location state.
 
**Facility Checks**
29. Credit Limit -- Credit Limit on the Facility must not be blank before
    approval.
30. Credit Hold -- If Credit Hold is Yes on the Facility, flag the
    placement and block approval.
 
**Travel Details**
31. Stipend Ceiling -- Stipend rates must not exceed the defined thresholds
    by business line.
32. Mileage Rate -- Mileage rate must not exceed the current IRS ceiling.
    Use a web search to confirm the current rate.
 
**System Sync**
33. BTE Sync Status -- Approved (Start status) placements must be synced
    to BTE. Check BTE Sync Status.
34. BTE Sync Integrity -- BTE Sync Status must not show Failed.
35. Purchase Order -- If the company requires a PO, Purchase Order must be
    present on the Placement or Candidate record.
36. Custom Object Flow-Down -- Custom object data from the Job or Candidate
    must have correctly flowed to the Placement.
 
**VMS / MSP**
37. Billing Profile Name -- Billing Profile name must match the required
    naming criteria for this client.
38. VMS Fields -- If Order Type = VMS, VMS Assignment Number, VMS Employee
    ID, and VMS Requisition ID must all be populated.
 
**Cross-Placement**
39. Mark-up % Consistency -- Calculate Mark-up % as (Bill Rate - Pay
    Rate) / Pay Rate. Flag if Mark-up % is inconsistent with other
    Approved placements for the same client.
 
### Output Format
Return "Audit Passed" if all aspects of the audit passed, "Audit
encountered an error" if the audit did not complete properly, or a
one-sentence description of which audit checks failed.
 
Followed by two blank lines and then a single markdown table:
 
| # | Check | Result | Reasoning |
|---|-------|--------|-----------|
| 1 | Example Check | ✅ | Condition met -- values confirmed |
| 2 | Example Check | ❌ | Value was blank -- required field |
 
### Structured Output
Set success to false if any check fails.
Set message to the rendered markdown table.
Only return "success": true if every check passes.
 
{
  "success": false,
  "message": "| # | Check | Result | Reasoning |\n|---|..."
}

For this Rate Card, I want to run an audit and check for the following
items. For a Rate Card to pass audit, all of the following must be true.
Please evaluate all of the following conditions.
 
Each check produces a ✅ pass or ❌ fail result with reasoning.
 
**Rate Relationships**
1.  OT >= 1.5x Regular -- OT pay rate must be at least 1.5x the regular
    (REG) rate across all rate types.
2.  Holiday >= OT Rate -- Holiday pay rate must be greater than or equal
    to the OT rate.
3.  Penalty Codes = Regular Rate -- Penalty earn code rates must equal the
    regular rate.
4.  Pay < Bill Rate -- Pay Rate must be less than Bill Rate, unless Pre-Bill
    Flag is Yes (in which case a $0 bill rate on the base earn code is
    acceptable).
5.  CA Meal & Rest Premiums -- If placement state is California, CA Meal
    Premium and CA Rest Premium earn codes must be present on the rate card.
    If not in CA, mark as ✅ N/A.
6.  Minimum Wage -- Base pay rate must meet or exceed the minimum wage for
    the placement city/state. Use a web search to confirm the current rate.
 
**Rate Card Status & Completeness**
7.  Active Status -- Rate card must be in Active status with an effective
    date on or before the placement Start Date.
8.  Holiday Earn Code -- Holiday earn code must be present on all W2
    Full-Time placements.
9.  Per Diem Earn Code -- Per diem placements must have the per diem earn
    code on the rate card.
10. $0 Pay Rate Warning -- If the base earn code (REG) Pay Rate is $0,
    return a warning unless a Daily, CPT, or PER earn code is also present.
11. $0 Bill Rate Warning -- If the base earn code (REG) Bill Rate is $0,
    return a warning unless a Daily, CPT, or PER earn code is also present.
 
**Client Comparison**
12. Earn Code Consistency -- Earn codes must be consistent with other active
    placements for the same client (accounting for payroll batch). Flag any
    earn codes present here but absent on others, or missing here but on
    others.
13. Bill Rate & Margin Consistency -- Bill rate and effective margin must be
    consistent with other active placements for the same client. Flag
    variances.
 
### Output Format
Return "Audit Passed" if all aspects of the audit passed, "Audit
encountered an error" if the audit did not complete properly, or a
one-sentence description of which audit checks failed.
 
Followed by two blank lines and then a single markdown table:
 
| # | Check | Result | Reasoning |
|---|-------|--------|-----------|
| 1 | Example Check | ✅ | Condition met -- values confirmed |
| 2 | Example Check | ❌ | Value was blank -- required field |
 
### Structured Output
Set success to false if any check fails.
Set message to the rendered markdown table.
Only return "success": true if every check passes.
 
{
  "success": false,
  "message": "| # | Check | Result | Reasoning |\n|---|..."
}

For this Payable Charge, I want to run an audit and check for the
following items. For a Payable Charge to pass audit, all of the following
must be true. Please evaluate all of the following conditions.

Each check produces a ✅ pass or ❌ fail result with reasoning.

**Rate Validation**
1.  OT Rate = 1.5x Regular -- OT earn code rate must be exactly 1.5x the
    regular (REG) rate on this charge.
2.  CA Double-Time -- If placement is in California, double-time rate must
    be >= 2x the regular rate. If not in CA, mark as ✅ N/A.
3.  Pay Rate Ceiling -- Pay Rate must not exceed the configured maximum pay
    rate for your firm.
4.  Pay Rate Floor -- Pay Rate must not fall below the configured minimum
    pay rate for your firm.
5.  Pay <= Bill Rate -- Pay Rate must not be greater than the Bill Rate.

**Hours Validation**
6.  Regular Hours <= 40 -- Regular Hours must not exceed 40 unless the
    worker is overtime-exempt or classified as 1099.
7.  OT Hours Threshold -- OT hours must not exceed the configured OT hours
    threshold for your firm.
8.  Holiday Overlap -- If holiday earn code hours are present, no regular
    hours should be logged for the same time window.

**Amount & Margin**
9.  Pay Amount Ceiling -- Total pay amount must not exceed the configured
    maximum pay amount per charge for your firm.
10. Pay <= Bill Amount -- Total pay amount must not exceed total bill amount.
11. Margin Floor -- Total payable amount must not exceed the configured
    margin floor percentage of total billable.
12. Corresponding Bill Record -- Payable charge must have a corresponding
    bill record where billing is expected.
13. Anomaly Detection -- Paycheck total must not be more than 20% above or
    below the worker's average across the prior 3 payable charges.

**Earn Code Matching**
The corresponding billable charge is defined as the billable charge for
the same placement with the same week-ending date.

14. Hours Match by Earn Code -- Total hours by earn code on payable must
    match the corresponding billable charge, excluding pay-only earn codes.
15. CA Total Hours Match -- For CA placements: total hours on payable must
    match the corresponding billable charge. Earn code-level match is not
    required due to CA OT rules. If not in CA, mark as ✅ N/A.

### Output Format
Return "Audit Passed" if all aspects of the audit passed, "Audit
encountered an error" if the audit did not complete properly, or a
one-sentence description of which audit checks failed.

Followed by two blank lines and then a single markdown table:

| # | Check | Result | Reasoning |
|---|-------|--------|-----------|
| 1 | Example Check | ✅ | Condition met -- values confirmed |
| 2 | Example Check | ❌ | Value was blank -- required field |

### Structured Output
Set success to false if any check fails.
Set message to the rendered markdown table.
Only return "success": true if every check passes.

{
  "success": false,
  "message": "| # | Check | Result | Reasoning |\n|---|..."
}

For this Billable Charge and its associated transactions, I want to run
an audit and check for the following items. For a Charge to pass audit,
all of the following must be true. Please evaluate all of the following
conditions.

Each check produces a ✅ pass or ❌ fail result with reasoning.

The corresponding PC is defined as the payable charge with the same
placement ID and week ending date.

**Audit Checks**
1.  Reg Check -- Reg hours are less than or equal to 40 if the employee
    type is W2 and not exempt.
2.  OT Check -- Overtime hours should be below 10 and if the placement
    location is not in CA, Reg hours should be = 40 if any OT is present.
3.  DT Check -- Doubletime hours should be below 5.
4.  Total Hours -- Total worked hours should be below 60.
5.  Total Spend -- Total dollars below $1,000.
6.  Duplicate Hours -- The Charge does not have duplicate transactions for
    each day that are identical.
7.  Drift Detection -- The total amount of the Billable Charge is not more
    than 20% higher than the average of the previous three Billable Charges
    for this placement.
8.  Payroll Export -- The corresponding PC is exported for payroll.
9.  Payable Match -- The corresponding PC has the same hours as the
    Billable Charge.
10. Payable Spend Check -- The corresponding PC has a lower dollar total
    than the Billable Charge.
11. Purchase Order -- If the invoice terms for this placement require a
    purchase order, every transaction on this Billable Charge must have a
    purchase order identified. Fail if any transaction is missing a PO
    when one is required.

### Output Format
Return "Audit Passed" if all aspects of the audit passed, "Audit
encountered an error" if the audit did not complete properly, or a
one-sentence description of which audit checks failed.

Followed by two blank lines and then a single markdown table:

| # | Check | Result | Reasoning |
|---|-------|--------|-----------|
| 1 | Reg Check | ✅ | 38 reg hours; W2 non-exempt |
| 2 | OT Check | ❌ | 12 OT hours; exceeds threshold of 10 |

### Structured Output
Set success to false if any check fails.
Set message to the rendered markdown table.
Only return "success": true if every check passes.

{
  "success": false,
  "message": "| # | Check | Result | Reasoning |\n|---|..."
}

Review all billable charges associated with purchase orders. For each PO, evaluate all of the following conditions. Each check produces a ✅ pass, ❌ fail, or ⚠️ warning result with reasoning.

This must cover every billable charge associated with the Purchase Order for the entire history of that PO — not just the charge the audit was launched from, not just recent charges, and not just one placement.



Finding the charges — do this before evaluating any check
How Purchase Orders are linked
The Purchase Order is not a field on the Billable Charge and not a field on the Bill Master Transaction. It is reached only through the Customer Required Field chain on the Bill Master:

BillableCharge

  └─ billMasters                          (to-many)

       └─ customerRequiredFields          (to-many) → BillMasterCustomerRequiredField

            ├─ customerRequiredFieldMeta  → valueType

            └─ customerRequiredFieldOption

                 └─ associatedEntityID    → the Purchase Order ID

Rules:

Only treat a Customer Required Field as a Purchase Order link when customerRequiredFieldMeta.valueType is Purchase Order (3). Ignore Text (1) and Custom Picker (2).

The PO identity is customerRequiredFieldOption.associatedEntityID.

A billable charge belongs to a PO if any of its bill masters resolve to that PO.

Where a charge splits across multiple POs, count only the bill masters resolving to the PO under evaluation.

If two different CRF Metas resolve to the same Purchase Order ID, flag it as a configuration issue and name both.

Gather the full history
For each Purchase Order in scope, search the entire corporation for every billable charge that has ever resolved to that PO.

Do not limit by placement, candidate, client contact, or date range.

Include invoiced and uninvoiced charges alike.

Include charges dated before the PO start date if any exist, and flag them.

If the search had to be bounded for any reason, state the bound applied.

State the number of charges found per PO before evaluating the checks.

How to total consumption
Do not sum BillMaster.amount. Sum BillMasterTransaction.netAmount across all transactions whose parent Bill Master resolves to the PO:

Exclude transactions where isDeleted is true.

Exclude transactions where isUnbillable is true. Report their count and value separately.

Include reversals — a transaction with reversalOfTransaction populated offsets its original, and both must be counted so the net is correct.

Include adjustments — where adjustmentSequenceNumber is greater than zero, count all sequence numbers.

If netAmount is unavailable, fall back to amount and say so.

Never abort. If a field or related record cannot be retrieved, mark that check ⚠️ with the specific reason and continue with every remaining check and PO.



Validation Checks
Missing PO — Billable charges where no purchase order number is present

Exceeded PO Amount — Charges where the cumulative billed total exceeds the authorized PO limit

Expired PO — Charges dated after the PO's expiration date

PO/Client Mismatch — Charges where the PO number does not match the PO on file for that client corporation

Inactive PO — Charges referencing a PO that has been marked inactive or closed

Utilization Summary
Total Charges to Date — Count and total dollar amount of all billable charges against this PO from the PO start date through today

Invoiced vs. Uninvoiced — Of the total billed amount, the sum and count of charges that have been invoiced, and the sum and count that have not yet been invoiced. Return a ⚠️ warning if the uninvoiced amount alone would push the PO into exhaustion once processed.

Remaining Balance — PO authorized amount minus total billed to date (invoiced + uninvoiced)

12-Week Average Weekly Spend — Average weekly billable charge amount over the trailing 12 weeks, anchored to today's date. Every charge counts toward Total Billed regardless of the window; the window governs the average only.

Forecast
Projected Weeks Remaining — Remaining PO balance ÷ 12-week average weekly spend

Projected Exhaustion Date — Today's date plus projected weeks remaining

Risk Flag — Flag ❌ if the PO is projected to be exhausted within 4 weeks, or if the projected exhaustion date falls before the PO's stated end date

Where a PO attribute needed by a check is not exposed on the Purchase Order record — authorized amount, start or end date, active status — return ⚠️ for that check with the reason, rather than ✅ or ❌. If the authorized amount cannot be read, checks 8, 10, 11, and 12 all return ⚠️.



Output Format
Return "Audit Passed" if all checks passed, "Audit encountered an error" if the audit did not complete properly, or a one-sentence description of which checks failed.

Followed by two blank lines and then a summary card for each PO.

PO card
PO #[PO Number] — [Client Name]

Check results

#

Check

Result

Reasoning

 
1

Missing PO

✅

All 47 billable charges have a PO number present

 
2

Exceeded PO Amount

❌

Cumulative billed total of $101,220.10 exceeds authorized limit of $100,000.00

All twelve checks must appear as rows, in order, with no omissions. A check that could not be evaluated shows ⚠️ and the reason — the row is never left out.

All billable charges on this PO

Every charge for the full history of the PO:

Billable charge

Placement

Candidate

Charge date

Amount to This PO

Full Charge Amount

Split?

Invoiced?

Running Total





Sort by charge date ascending so the Running Total builds chronologically. Where Split? is Yes, name the other Purchase Orders beneath the table. Mark the source charge if the audit was launched from one.

If more than 100 charges exist, show the 100 most recent, state the total count and value withheld, and confirm the totals cover all of them.

Charges by placement

Placement

Candidate

Charges

Amount to This PO

% of PO

First

Last






Sort by amount descending.

Utilization

Field

Value

 
Authorized Amount

$X,XXX.XX

 
Total Billed to Date

$X,XXX.XX (N charges)

 
→ Invoiced

$X,XXX.XX (N charges)

 
→ Not Yet Invoiced

$X,XXX.XX (N charges)

 
Remaining Balance

$X,XXX.XX

 
12-Week Avg Weekly Spend

$X,XXX.XX

 
Projected Weeks Remaining

X.X weeks

 
Projected Exhaustion Date

Month DD, YYYY

 
PO End Date

Month DD, YYYY

Excluded transactions

State the count and value of transactions excluded from Total Billed, by reason (deleted, unbillable), or "None — all transactions counted."

Crossing point

Where Total Billed exceeds the Authorized Amount, name the first charge at which the running total passed the limit — its ID, date, amount, and the running total at that point.




Portfolio summary — after all PO cards
Purchase Order

PO #

Client

Authorized

Total Billed

Remaining

% Used

Charges

Exhaustion Date

Result






Then state:

Total POs reviewed

Count passing, count with warnings, count failing

Count where the authorized amount could not be read

Total billable charges examined across all POs

Combined authorized, combined billed, combined remaining

Earliest projected exhaustion date and which PO it belongs to

Where any individual PO has exceeded its allocation while the combined position is healthy, print this verbatim:

Note: the combined position is under allocation, but Purchase Order budgets are not fungible. PO #[number] has individually exceeded its authorized amount by $X,XXX.XX. The combined surplus does not offset it.

Method notes
Customer Required Field Meta name and ID used for each PO link, confirming valueType was Purchase Order (3)

CRF Option display label and associatedEntityID matched

Whether the search covered the full corporation or was bounded

Whether netAmount was used, or the fallback to amount

Any records that could not be read, and why

Any duplicate CRF Metas resolving to the same Purchase Order ID




Structured Output
Set success to false if any check fails across any PO, or if combined billed exceeds combined authorized. Set message to the full rendered output including all PO cards and the portfolio summary. Only return "success": true if every check passes on every PO. Checks returning ⚠️ do not by themselves cause failure.

json

Followed by two blank lines and then a single markdown table: | # | Check | Result | Reasoning | |---|-------|--------|-----------| | 1 | Example Check | ✅ | Condition met -- values confirmed | | 2 | Example Check | ❌ | Value was blank -- required field | ### Structured Output Set success to false if any check fails. Set message to the rendered markdown table. Only return "success": true if every check passes. {   "success": false,   "message": "| # | Check | Result | Reasoning |\n|---|..." } 

For this Candidate record, I want to run an audit and check for the
following items. For a Candidate to pass audit, all of the following must
be true. Please evaluate all of the following conditions.

Each check produces a ✅ pass or ❌ fail result with reasoning.

**Contact & Identity**
1.  Primary Phone -- Primary Phone must not be blank. Fail if all digits
    are the same repeated integer (e.g., 1111111111).
2.  Address Completeness -- Street, City, and State must not be blank.
    State must not be abbreviated.
3.  Zip Code -- Zip Code must not be blank. US addresses must be formatted
    as 5 digits.
4.  Email 1 -- Email 1 must not be blank, must contain @, and must not
    contain a URL.
5.  EEO Fields -- Gender, Ethnicity, and Citizenship must be populated
    where required for compliance and EEO reporting.

**Job Readiness**
6.  Desired Pay Rate -- Desired Pay Rate must not be blank.
7.  Resume Currency -- Most recent resume file must not be older than 6
    months from today. Check via file attachment date.

**Compliance & Onboarding**
8.  Background & Drug Test -- Background Check and Drug Test completion
    must be confirmed where required.
9.  Tax State Consistency -- Tax State on the Candidate record must match
    the Placement Worksite Location state.
10. Onboarding Forms -- Core and client onboarding forms must be confirmed
    on file.
11. Identity Spot Check -- Confirm name, date of birth, SSN, and address
    are present and plausible. Flag obvious errors or test data.
12. Direct Deposit -- Direct Deposit form must be completed and banking
    information (routing and account number) must be confirmed back in the
    system.
13. E-Verify Status -- E-Verify Status must show "Employment Authorized"
    -- not just initiated or submitted.
14. Onboarding Status -- Onboarding Status must confirm onboarding is
    started or completed. Any override must be intentional and documented.
15. Payroll Sync Status -- Payroll Sync Status must confirm the candidate
    is synced to the payroll system.

### Output Format
Return "Audit Passed" if all aspects of the audit passed, "Audit
encountered an error" if the audit did not complete properly, or a
one-sentence description of which audit checks failed.

Followed by two blank lines and then a single markdown table:

| # | Check | Result | Reasoning |
|---|-------|--------|-----------|
| 1 | Example Check | ✅ | Condition met -- values confirmed |
| 2 | Example Check | ❌ | Value was blank -- required field |

### Structured Output
Set success to false if any check fails.
Set message to the rendered markdown table.
Only return "success": true if every check passes.

{
  "success": false,
  "message": "| # | Check | Result | Reasoning |\n|---|..."
}

For this Placement, I want to run a timesheet activity audit. For a
Placement to pass this audit, the following must be true. Please evaluate
the following condition.

Each check produces a ✅ pass or ❌ fail result with reasoning.

**Activity Monitoring**
1.  Lapsed Activity -- Active placements with no timesheet submitted for
    3 or more consecutive weeks should be flagged as likely ended. These
    must be reviewed and the placement status updated if the worker is no
    longer active.

### Output Format
Return "Audit Passed" if all aspects of the audit passed, "Audit
encountered an error" if the audit did not complete properly, or a
one-sentence description of which audit checks failed.

Followed by two blank lines and then a single markdown table:

| # | Check | Result | Reasoning |
|---|-------|--------|-----------|
| 1 | Example Check | ✅ | Condition met -- values confirmed |
| 2 | Example Check | ❌ | Value was blank -- required field |

### Structured Output
Set success to false if any check fails.
Set message to the rendered markdown table.
Only return "success": true if every check passes.

{
  "success": false,
  "message": "| # | Check | Result | Reasoning |\n|---|..."
}