💼 Business

Wave Invoice Estimate Field Map from Ledger Inventory (No Invented Revenue Totals)

Turn a Wave ledger inventory into an invoice estimate field map only. No invented revenue totals, tax rates, or payment scores beyond the inventory.

0.0
0Reviews
P
September 24, 2026

Prompt

Act as a Wave invoice-estimate field cartographer who only uses a pasted inventory. You write a invoice estimate field map the inventory already supports. You do not invent revenue totals, tax rates, payment scores, or billing secrets not in Inputs. This is not a Wave brand-kit generator; not a bookkeeping guarantee.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Inventory I lock (invoice stubs, estimate cues, client notes): [Inventory]
- Wave / account version notes I lock: [Version]
- Business or ledger label I may quote (or UNKNOWN): [Workspace]
- Required invoice or map names I may quote (or UNKNOWN): [SpecNames]
- Invoice and estimate labels already present (or UNKNOWN): [InvoiceCues]
- Field and line-item labels already present (or UNKNOWN): [FieldCues]
- Client and contact notes already present (or UNKNOWN): [ClientNotes]
- Words I must not use: [Banned]
- What I must never invent (revenue totals, tax rates, payment scores, billing secrets): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, InvoiceCues, FieldCues, ClientNotes, Lang. Forbidden: invented revenue totals, tax rates, payment scores, billing secrets. Banner: not a Wave brand-kit generator; not a bookkeeping guarantee.
2. Invoice estimate field map: one numbered row per Inventory stub or cue. Missing ClientNotes write NOT IN INPUTS. Use Wave invoices, estimates, fields, and client language when Inventory supports it. Never print revenue-count or tax VALUES not in Inventory.
3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent payment-score VALUES not in Inventory.
4. Version lock: print Version. Refuse Wave features newer than Version if Version is named.
5. Refuse list: inventing revenue totals, inventing tax rates, inventing payment scores, inventing billing secrets.
6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.

Constraints:
- Map from Inventory only. No invented revenue VALUES. Teach Wave invoice estimate field maps, not a QuickBooks or FreshBooks swap.
- Honor Version. No emojis.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Generated Output

This image was generated using the prompt above.

Wave Invoice Estimate Field Map from Ledger Inventory (No Invented Revenue Totals) - Result

Examples

Example Input

Inventory: invoice Harbor Quay Dock Retainer as pasted field cue Quay Hours as pasted client notes Studio as pasted; invoice River Ops River Retainer as pasted field cue Quay Hours as pasted. Revenue invent NONE. Tax invent NONE.
Version: Wave as pasted (do not invent unreleased AI revenue pack)
Workspace: Harbor Quay bookkeeping desk as pasted
SpecNames: Dock Retainer invoice map as pasted; River Retainer invoice map as pasted. Payment scores UNKNOWN.
InvoiceCues: Dock Retainer as pasted; River Retainer as pasted. Credit UNKNOWN.
FieldCues: Quay Hours as pasted. Discount UNKNOWN.
ClientNotes: Studio as pasted. Revenue VALUES NOT IN INPUTS.
Banned: guaranteed revenue, revenue invent, tax invent, payment invent
Never: invent revenue totals, invent tax rates, invent payment scores, invent billing secrets
Format: ledger + table + specs + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: invoice Harbor Quay Dock Retainer as pasted field cue Quay Hours as pasted client notes Studio as pasted; invoice River Ops River Retainer as pasted field cue Quay Hours as pasted. Revenue invent NONE. Tax invent NONE. Version Wave as pasted. Workspace Harbor Quay bookkeeping desk. SpecNames Dock Retainer invoice map as pasted; River Retainer invoice map as pasted. Payment scores UNKNOWN. InvoiceCues Dock Retainer as pasted; River Retainer as pasted. Credit UNKNOWN. FieldCues Quay Hours as pasted. Discount UNKNOWN. ClientNotes Studio as pasted. Revenue VALUES NOT IN INPUTS. Lang English. Banner: not a Wave brand-kit generator; not a bookkeeping guarantee. Forbidden: invented revenue totals, tax rates, payment scores, billing secrets, guaranteed revenue, revenue invent, tax invent, payment invent.

2. Invoice estimate field map.
1. Harbor Quay Dock Retainer | InvoiceCues Dock Retainer as pasted | FieldCues Quay Hours as pasted | ClientNotes Studio as pasted | revenue VALUES NONE | tax NONE | Wave invoice estimate field map only.
2. River Ops River Retainer | InvoiceCues River Retainer as pasted | FieldCues Quay Hours as pasted | ClientNotes beyond Studio NOT IN INPUTS | revenue VALUES NONE | tax NONE.
Payment scores UNKNOWN so write payment-score VALUES NOT IN INPUTS. Credit not invented beyond InvoiceCues.

3. Spec name set. Dock Retainer invoice map as pasted; River Retainer invoice map as pasted as SpecNames. Unnamed rows NOT IN INPUTS. Never invent payment-score VALUES.

4. Version lock. Wave as pasted as pasted. Refuse unreleased AI revenue pack.

5. Refuse list. inventing revenue totals; inventing tax rates; inventing payment scores; inventing billing secrets.

6. Compliance. Quoted Banned: guaranteed revenue, revenue invent, tax invent, payment invent. Cut. Quoted Never: invent revenue totals, invent tax rates, invent payment scores, invent billing secrets. Cut. Format ledger + table + specs + version + refuse + compliance.

Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.

Reviews (0)

Please login to leave a review.
Loading reviews...