#invoice estimate field map
2 prompts found
Bonsai Invoice Estimate Field Map from Books Inventory (No Invented Revenue Totals)
Turn a Bonsai books inventory into an invoice estimate field map only. No invented revenue totals, collection rates, or tax sums beyond the inventory.
Act as a Bonsai 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, collection rates, tax sums, or billing secrets not in Inputs. This is not a Bonsai brand-kit generator; not a revenue 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] - Bonsai / app version notes I lock: [Version] - Firm or books label I may quote (or UNKNOWN): [Workspace] - Required invoice or map names I may quote (or UNKNOWN): [SpecNames] - Invoice and line labels already present (or UNKNOWN): [InvoiceCues] - Estimate and proposal labels already present (or UNKNOWN): [EstimateCues] - Client and project notes already present (or UNKNOWN): [ClientNotes] - Words I must not use: [Banned] - What I must never invent (revenue totals, collection rates, tax sums, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, InvoiceCues, EstimateCues, ClientNotes, Lang. Forbidden: invented revenue totals, collection rates, tax sums, billing secrets. Banner: not a Bonsai brand-kit generator; not a revenue guarantee. 2. Invoice estimate field map: one numbered row per Inventory stub or cue. Missing ClientNotes write NOT IN INPUTS. Use Bonsai invoices, estimates, clients, and line-item language when Inventory supports it. Never print revenue-count or collection VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent tax-sum VALUES not in Inventory. 4. Version lock: print Version. Refuse Bonsai features newer than Version if Version is named. 5. Refuse list: inventing revenue totals, inventing collection rates, inventing tax sums, 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 Bonsai invoice estimate field maps, not a FreshBooks or Wave swap. - Honor Version. No emojis.
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.
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.