Business
246 prompts in this category · Page 4 of 21
Toast POS Menu Build Sheet for a Restaurant Opening: Menu Groups, Modifier Groups, Pricing, and Prep Station Routing
Turn a printed menu and kitchen layout into a Toast POS build sheet before opening day: menus and menu groups, items, shared modifier groups with min and max selections, size and time pricing, sales categories, tax, and prep station routing.
Act as a restaurant POS implementation consultant who builds Toast menus for new openings. You build the menu once, the way the kitchen actually fires it, so servers are not hunting for buttons and tickets reach the right station. Inputs: - The menu as printed, with prices and any choice or add-on text: [MenuText] - Kitchen and bar stations, and which screens or printers they use: [Stations] - Sales categories the owner wants on reports (Food, N/A Beverage, Beer, Wine, Liquor): [SalesCategories] - Tax rules the accountant gave you, including anything taxed differently: [TaxRules] - Service periods and anything only sold in one of them: [Dayparts] - Ordering channels to support at launch (POS, online ordering, kiosk): [Channels] - Output format: [Format] - Language: [Lang] Generate: 1. Menu structure. Propose the Toast menus and menu groups from MenuText and Dayparts, in the order servers will tap them. Explain any group you split or merged. 2. Item rows as a build sheet table: menu group, item name (POS button name kept short), price or pricing strategy (base price, size price, time-specific price), sales category, tax rate, prep station, and the modifier groups attached. 3. Modifier groups. For every choice in MenuText, write a modifier group with its options, option prices, and selection rules (required or optional, minimum and maximum). Mark groups that should be shared across items so a price change happens once. 4. Prep station routing. Map every item and any modifier that needs its own ticket line to Stations, and say what Expo sees. Flag items that need two stations. 5. Channel settings from Channels: which items or groups are hidden online, which are alcohol and need the restaurant's alcohol rules, and naming that reads well to guests online. 6. Pre-opening test script: ring ten test orders that hit every modifier group and station, void them, and check the sales category and tax lines on the test report. Constraints: - Only items and prices that appear in MenuText; mark any missing price as PRICE NEEDED. - Use tax rates exactly as given in TaxRules; do not supply a rate yourself. - Use Toast terms (menu, menu group, item, modifier group, modifier option, prep station, sales category); if a setting name may differ in the owner's Toast version, say so. - No em dashes.
Xero Bank Rules Spec for Onboarding a New Bookkeeping Client (Spend, Receive, and Transfer Rules)
Turn a few months of a client's bank statement lines into a Xero bank rules spec: rule type, Any or All conditions, contact, account and tax rate allocations, rule order, and the lines that should never get a rule.
Act as a Xero-certified bookkeeper who sets up bank rules when onboarding small business clients. You write rules that are specific enough not to misfire, you know a rule only proposes a coding in the Reconcile tab and still needs OK, and you leave irregular items for human review. Inputs: - Recurring bank statement lines (date, payee or description, reference, amount, money in or out): [StatementLines] - Client chart of accounts codes and names in Xero: [ChartOfAccounts] - Tax region and the Xero tax rates in use (for example GST on Expenses, BAS Excluded): [TaxRates] - Tracking categories and options, if any: [Tracking] - Bank accounts connected in Xero (names as they appear): [BankAccounts] - Client context (industry, payment processor, owner drawings habits): [ClientContext] - Output format: [Format] Generate: 1. Pattern scan of StatementLines. Group lines by payee text and say which are fixed amount, variable amount, mixed purpose, or transfers between BankAccounts. 2. Rule spec table, one row per rule: rule title, rule type (Spend money, Receive money, or Transfer), Any or All, each condition as field plus operator plus value (Payee, Description, or Reference with contains, equals, or starts with; Amount where it truly distinguishes), contact to set, allocation lines with account code from ChartOfAccounts, tax rate from TaxRates, Fixed or Percent, tracking option, reference to set, and Run this rule on which bank account. 3. Processor payouts. If ClientContext includes a card processor that pays out net of fees, recommend a clearing account approach instead of a percent split guess, and show the rule that codes payouts to the clearing account. 4. Rule order. List the order the rules should sit in the Bank rules list, with more specific rules above broad ones, and why. 5. Lines that get no rule (owner purchases on the business card, one-off refunds, anything mixed) with what the bookkeeper should do instead. 6. Client questions to send before turning rules on. Constraints: - Use only account codes and tax rates from ChartOfAccounts and TaxRates; write NOT IN CHART if a needed account is missing. - Never use a condition so broad that it would catch an unrelated payee (for example contains 'AMZ' alone). - This is setup guidance, not tax advice; flag any tax rate choice the accountant should confirm. - No em dashes.
Ramp Expense Vendor Approval Route Checklist from Policy Notes (No Invented Reimbursement Totals)
Compile a Ramp expense-vendor-approval-route checklist from pasted policy notes only. No invented reimbursement totals, pay ranks, or finance scoreboards. Not a live Ramp sync.
Act as a Ramp expense-vendor-approval-route checklist engineer who only uses pasted policy notes. You compile an expense-vendor-approval-route checklist the notes already support. You do not invent reimbursement totals, pay ranks, finance scoreboards, or guaranteed payout claims. This is not a live Ramp sync, not an Expensify invent, and not finance or tax consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Policy notes I lock (expense stubs, vendor cues, approval-route fragments): [PolicyNotes] - Ramp workspace or version notes I lock: [Version] - Entity or workspace label I may quote (or UNKNOWN): [EntityLabel] - Expense titles already present (or UNKNOWN): [ExpenseTitles] - Vendor cues already present (or UNKNOWN): [VendorCues] - Approval cues already present (or UNKNOWN): [ApprovalCues] - Cost center cues already present (or UNKNOWN): [CostCenterCues] - Words I must not use: [Banned] - What I must never invent (reimbursement totals, pay ranks, finance scoreboards, guaranteed payout claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: PolicyNotes nouns, Version, EntityLabel, ExpenseTitles, VendorCues, ApprovalCues, CostCenterCues, Lang. Banner: not finance or tax consulting advice; not a live Ramp sync. Forbidden: invented reimbursement totals, pay ranks, finance scoreboards, guaranteed payout claims. 2. Expense-vendor-approval-route checklist: one checkbox row per ExpenseTitles entry. Attach only VendorCues and ApprovalCues named beside that expense in PolicyNotes. Missing vendor or approval write NOT IN INPUTS. 3. Cost center sketch: for each CostCenterCues entry, list expenses that name it. Do not invent a $1480 reimbursement claim if absent. 4. Entity caution block: quote EntityLabel and Version only. Card packs not in PolicyNotes stay NOT IN INPUTS. 5. Refuse list: inventing $1480 reimbursement totals, inventing pay ranks, inventing finance scoreboards, inventing guaranteed payout claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print expense and vendor counts from PolicyNotes only. Format as Format. Constraints: - Expense-vendor-approval-route checklist from PolicyNotes only. No invented reimbursement totals. - Honor Version. No emojis. Not a live Ramp dashboard. Not finance or tax consulting advice.
Certify Expense Vendor Approval Route Checklist from Policy Notes (No Invented Reimbursement Totals)
Compile a Certify expense-vendor-approval-route checklist from pasted policy notes only. No invented reimbursement totals, pay ranks, or finance scoreboards. Not a live Certify sync.
Act as a Certify expense-vendor-approval-route checklist engineer who only uses pasted policy notes. You compile an expense-vendor-approval-route checklist the notes already support. You do not invent reimbursement totals, pay ranks, finance scoreboards, or guaranteed payout claims. This is not a live Certify sync, not an Expensify invent, and not finance or tax consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Policy notes I lock (expense stubs, vendor cues, approval-route fragments): [PolicyNotes] - Certify workspace or version notes I lock: [Version] - Entity or workspace label I may quote (or UNKNOWN): [EntityLabel] - Expense titles already present (or UNKNOWN): [ExpenseTitles] - Vendor cues already present (or UNKNOWN): [VendorCues] - Approval cues already present (or UNKNOWN): [ApprovalCues] - Cost center cues already present (or UNKNOWN): [CostCenterCues] - Words I must not use: [Banned] - What I must never invent (reimbursement totals, pay ranks, finance scoreboards, guaranteed payout claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: PolicyNotes nouns, Version, EntityLabel, ExpenseTitles, VendorCues, ApprovalCues, CostCenterCues, Lang. Banner: not finance or tax consulting advice; not a live Certify sync. Forbidden: invented reimbursement totals, pay ranks, finance scoreboards, guaranteed payout claims. 2. Expense-vendor-approval-route checklist: one checkbox row per ExpenseTitles entry. Attach only VendorCues and ApprovalCues named beside that expense in PolicyNotes. Missing vendor or approval write NOT IN INPUTS. 3. Cost center sketch: for each CostCenterCues entry, list expenses that name it. Do not invent a $1620 reimbursement claim if absent. 4. Entity caution block: quote EntityLabel and Version only. Tax packs not in PolicyNotes stay NOT IN INPUTS. 5. Refuse list: inventing $1620 reimbursement totals, inventing pay ranks, inventing finance scoreboards, inventing guaranteed payout claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print expense and vendor counts from PolicyNotes only. Format as Format. Constraints: - Expense-vendor-approval-route checklist from PolicyNotes only. No invented reimbursement totals. - Honor Version. No emojis. Not a live Certify dashboard. Not finance or tax consulting advice.
Tipalti Expense Vendor Approval Route Checklist from Policy Notes (No Invented Reimbursement Totals)
Compile a Tipalti expense-vendor-approval-route checklist from pasted policy notes only. No invented reimbursement totals, pay ranks, or finance scoreboards. Not a live Tipalti sync.
Act as a Tipalti expense-vendor-approval-route checklist engineer who only uses pasted policy notes. You compile an expense-vendor-approval-route checklist the notes already support. You do not invent reimbursement totals, pay ranks, finance scoreboards, or guaranteed payout claims. This is not a live Tipalti sync, not a Bill.com invent, and not finance or tax consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Policy notes I lock (expense stubs, vendor cues, approval-route fragments): [PolicyNotes] - Tipalti workspace or version notes I lock: [Version] - Entity or workspace label I may quote (or UNKNOWN): [EntityLabel] - Expense titles already present (or UNKNOWN): [ExpenseTitles] - Vendor cues already present (or UNKNOWN): [VendorCues] - Approval route cues already present (or UNKNOWN): [ApprovalRouteCues] - Cost center cues already present (or UNKNOWN): [CostCenterCues] - Words I must not use: [Banned] - What I must never invent (reimbursement totals, pay ranks, finance scoreboards, guaranteed payout claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: PolicyNotes nouns, Version, EntityLabel, ExpenseTitles, VendorCues, ApprovalRouteCues, CostCenterCues, Lang. Banner: not finance or tax consulting advice; not a live Tipalti sync. Forbidden: invented reimbursement totals, pay ranks, finance scoreboards, guaranteed payout claims. 2. Expense-vendor-approval-route checklist: one checkbox row per ExpenseTitles entry. Attach only VendorCues and ApprovalRouteCues named beside that expense in PolicyNotes. Missing vendor or approval route write NOT IN INPUTS. 3. Cost center sketch: for each CostCenterCues entry, list expenses that name it. Do not invent a $1840 reimbursement claim if absent. 4. Entity caution block: quote EntityLabel and Version only. Tax packs not in PolicyNotes stay NOT IN INPUTS. 5. Refuse list: inventing $1840 reimbursement totals, inventing pay ranks, inventing finance scoreboards, inventing guaranteed payout claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print expense and vendor counts from PolicyNotes only. Format as Format. Constraints: - Expense-vendor-approval-route checklist from PolicyNotes only. No invented reimbursement totals. - Honor Version. No emojis. Not a live Tipalti dashboard. Not finance or tax consulting advice.
Expensify Expense Vendor Approval Route Checklist from Policy Notes (No Invented Reimbursement Totals)
Compile an Expensify expense-vendor-approval-route checklist from pasted policy notes only. No invented reimbursement totals, spend ranks, or finance scoreboards. Not a live Expensify sync.
Act as an Expensify expense-vendor-approval-route checklist engineer who only uses pasted policy notes. You compile an expense-vendor-approval-route checklist the notes already support. You do not invent reimbursement totals, spend ranks, finance scoreboards, or guaranteed payout claims. This is not a live Expensify sync, not an Emburse invent, and not finance consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Policy notes I lock (expense stubs, vendor cues, approval fragments): [PolicyNotes] - Expensify workspace or version notes I lock: [Version] - Workspace or policy label I may quote (or UNKNOWN): [PolicyLabel] - Expense titles already present (or UNKNOWN): [ExpenseTitles] - Vendor cues already present (or UNKNOWN): [VendorCues] - Approval cues already present (or UNKNOWN): [ApprovalCues] - Category cues already present (or UNKNOWN): [CategoryCues] - Words I must not use: [Banned] - What I must never invent (reimbursement totals, spend ranks, finance scoreboards, guaranteed payout claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: PolicyNotes nouns, Version, PolicyLabel, ExpenseTitles, VendorCues, ApprovalCues, CategoryCues, Lang. Banner: not finance consulting advice; not a live Expensify sync. Forbidden: invented reimbursement totals, spend ranks, finance scoreboards, guaranteed payout claims. 2. Expense-vendor-approval-route checklist: one checkbox row per ExpenseTitles entry. Attach only VendorCues and ApprovalCues named beside that expense in PolicyNotes. Missing vendor or approval write NOT IN INPUTS. 3. Category sketch: for each CategoryCues entry, list expenses that name it. Do not invent a 2400 reimbursement-total claim if absent. 4. Policy caution block: quote PolicyLabel and Version only. Receipt packs not in PolicyNotes stay NOT IN INPUTS. 5. Refuse list: inventing 2400 reimbursement totals, inventing spend ranks, inventing finance scoreboards, inventing guaranteed payout claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print expense and vendor counts from PolicyNotes only. Format as Format. Constraints: - Expense-vendor-approval-route checklist from PolicyNotes only. No invented reimbursement totals. - Honor Version. No emojis. Not a live Expensify dashboard. Not finance consulting advice.
Emburse Expense Report Approval Route Checklist from Policy Notes (No Invented Reimbursement Totals)
Compile an Emburse expense-report-approval-route checklist from pasted policy notes only. No invented reimbursement totals, spend ranks, or finance scoreboards. Not a live Emburse sync.
Act as an Emburse expense-report-approval-route checklist engineer who only uses pasted policy notes. You compile an expense-report-approval-route checklist the notes already support. You do not invent reimbursement totals, spend ranks, finance scoreboards, or approval percents. This is not a live Emburse sync, not an Expensify invent, and not finance or tax consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Policy notes I lock (report stubs, approval cues, route fragments): [PolicyNotes] - Emburse workspace or version notes I lock: [Version] - Org or cost-center label I may quote (or UNKNOWN): [OrgLabel] - Report titles already present (or UNKNOWN): [ReportTitles] - Approval cues already present (or UNKNOWN): [ApprovalCues] - Route cues already present (or UNKNOWN): [RouteCues] - Vendor cues already present (or UNKNOWN): [VendorCues] - Words I must not use: [Banned] - What I must never invent (reimbursement totals, spend ranks, finance scoreboards, approval percents): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: PolicyNotes nouns, Version, OrgLabel, ReportTitles, ApprovalCues, RouteCues, VendorCues, Lang. Banner: not finance or tax consulting advice; not a live Emburse sync. Forbidden: invented reimbursement totals, spend ranks, finance scoreboards, approval percents. 2. Expense-report-approval-route checklist: one checkbox row per ReportTitles entry. Attach only ApprovalCues and RouteCues named beside that report in PolicyNotes. Missing approval or route write NOT IN INPUTS. 3. Vendor sketch: for each VendorCues entry, list reports that name it. Do not invent a $1840 reimbursement claim if absent. 4. Org caution block: quote OrgLabel and Version only. Receipt packs not in PolicyNotes stay NOT IN INPUTS. 5. Refuse list: inventing $1840 reimbursement totals, inventing spend ranks, inventing finance scoreboards, inventing approval percents. 6. Compliance pass: quote Banned and Never hits. Cut them. Print report and route counts from PolicyNotes only. Format as Format. Constraints: - Expense-report-approval-route checklist from PolicyNotes only. No invented reimbursement totals. - Honor Version. No emojis. Not a live Emburse dashboard. Not finance or tax consulting advice.
Ramp Bill Expense Vendor Route Checklist from Policy Notes (No Invented Reimbursement Totals)
Compile a Ramp bill-expense-vendor route checklist from pasted policy notes only. No invented reimbursement totals, spend ranks, or finance scoreboards. Not a live Ramp sync.
Act as a Ramp bill-expense-vendor route checklist engineer who only uses pasted policy notes. You compile a bill-expense-vendor route checklist the notes already support. You do not invent reimbursement totals, spend ranks, finance scoreboards, or savings claims. This is not a live Ramp sync, not an Expensify invent, and not accounting consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Policy notes I lock (bill stubs, expense cues, vendor fragments): [PolicyNotes] - Ramp workspace or version notes I lock: [Version] - Entity or card program label I may quote (or UNKNOWN): [EntityLabel] - Bill titles already present (or UNKNOWN): [BillTitles] - Expense cues already present (or UNKNOWN): [ExpenseCues] - Vendor cues already present (or UNKNOWN): [VendorCues] - Approval cues already present (or UNKNOWN): [ApprovalCues] - Words I must not use: [Banned] - What I must never invent (reimbursement totals, spend ranks, finance scoreboards, savings claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: PolicyNotes nouns, Version, EntityLabel, BillTitles, ExpenseCues, VendorCues, ApprovalCues, Lang. Banner: not accounting consulting advice; not a live Ramp sync. Forbidden: invented reimbursement totals, spend ranks, finance scoreboards, savings claims. 2. Bill-expense-vendor route checklist: one checkbox row per BillTitles entry. Attach only ExpenseCues and VendorCues named beside that bill in PolicyNotes. Missing expense or vendor write NOT IN INPUTS. 3. Approval sketch: for each ApprovalCues entry, list bills that name it. Do not invent a $18,400 reimbursement-total claim if absent. 4. Entity caution block: quote EntityLabel and Version only. GL packs not in PolicyNotes stay NOT IN INPUTS. 5. Refuse list: inventing $18,400 reimbursement totals, inventing spend ranks, inventing finance scoreboards, inventing savings claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print bill and vendor counts from PolicyNotes only. Format as Format. Constraints: - Bill-expense-vendor route checklist from PolicyNotes only. No invented reimbursement totals. - Honor Version. No emojis. Not a live Ramp dashboard. Not accounting consulting advice.
Expensify Report Category Receipt Checklist from Policy Notes (No Invented Reimbursement Totals)
Compile an Expensify report category-receipt checklist from pasted policy notes only. No invented reimbursement totals, approval ranks, or spend scoreboards. Not a live Expensify sync.
Act as an Expensify report category-receipt checklist engineer who only uses pasted policy notes. You compile a report category-receipt checklist the notes already support. You do not invent reimbursement totals, approval ranks, spend scoreboards, or tax claims. This is not a live Expensify sync, not a Melio invent, and not accounting or tax advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Policy notes I lock (report stubs, category cues, receipt fragments): [PolicyNotes] - Expensify workspace or version notes I lock: [Version] - Company or entity label I may quote (or UNKNOWN): [CompanyLabel] - Report titles already present (or UNKNOWN): [ReportTitles] - Category cues already present (or UNKNOWN): [CategoryCues] - Receipt cues already present (or UNKNOWN): [ReceiptCues] - Approver cues already present (or UNKNOWN): [ApproverCues] - Words I must not use: [Banned] - What I must never invent (reimbursement totals, approval ranks, spend scoreboards, tax claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: PolicyNotes nouns, Version, CompanyLabel, ReportTitles, CategoryCues, ReceiptCues, ApproverCues, Lang. Banner: not accounting or tax advice; not a live Expensify sync. Forbidden: invented reimbursement totals, approval ranks, spend scoreboards, tax claims. 2. Report category-receipt checklist: one checkbox row per ReportTitles entry. Attach only CategoryCues and ReceiptCues named beside that report in PolicyNotes. Missing category or receipt write NOT IN INPUTS. 3. Approver sketch: for each ApproverCues entry, list reports that name it. Do not invent a $1850 reimbursement-total claim if absent. 4. Company caution block: quote CompanyLabel and Version only. Card packs not in PolicyNotes stay NOT IN INPUTS. 5. Refuse list: inventing $1850 reimbursement totals, inventing approval ranks, inventing spend scoreboards, inventing tax claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print report and category counts from PolicyNotes only. Format as Format. Constraints: - Report category-receipt checklist from PolicyNotes only. No invented reimbursement totals. - Honor Version. No emojis. Not a live Expensify dashboard. Not accounting or tax advice.
QuickBooks Online Bill Payment Vendor Route Checklist from Policy Notes (No Invented Reimbursement Totals)
Compile a QuickBooks Online bill payment vendor-route checklist from pasted policy notes only. No invented reimbursement totals, approval ranks, or cash scoreboards. Not a live QuickBooks sync.
Act as a QuickBooks Online bill payment vendor-route checklist engineer who only uses pasted policy notes. You compile a bill payment vendor-route checklist the notes already support. You do not invent reimbursement totals, approval ranks, cash scoreboards, or tax claims. This is not a live QuickBooks sync, not a Melio invent, and not accounting or tax advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Policy notes I lock (bill stubs, payment cues, vendor fragments): [PolicyNotes] - QuickBooks Online company or version notes I lock: [Version] - Company or entity label I may quote (or UNKNOWN): [CompanyLabel] - Bill titles already present (or UNKNOWN): [BillTitles] - Payment cues already present (or UNKNOWN): [PaymentCues] - Vendor cues already present (or UNKNOWN): [VendorCues] - Route cues already present (or UNKNOWN): [RouteCues] - Words I must not use: [Banned] - What I must never invent (reimbursement totals, approval ranks, cash scoreboards, tax claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: PolicyNotes nouns, Version, CompanyLabel, BillTitles, PaymentCues, VendorCues, RouteCues, Lang. Banner: not accounting or tax advice; not a live QuickBooks sync. Forbidden: invented reimbursement totals, approval ranks, cash scoreboards, tax claims. 2. Bill payment vendor-route checklist: one checkbox row per BillTitles entry. Attach only PaymentCues and VendorCues named beside that bill in PolicyNotes. Missing payment or vendor write NOT IN INPUTS. 3. Route sketch: for each RouteCues entry, list bills that name it. Do not invent a $4,200 reimbursement-total claim if absent. 4. Company caution block: quote CompanyLabel and Version only. Bank packs not in PolicyNotes stay NOT IN INPUTS. 5. Refuse list: inventing $4,200 reimbursement totals, inventing approval ranks, inventing cash scoreboards, inventing tax claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print bill and vendor counts from PolicyNotes only. Format as Format. Constraints: - Bill payment vendor-route checklist from PolicyNotes only. No invented reimbursement totals. - Honor Version. No emojis. Not a live QuickBooks dashboard. Not accounting or tax advice.
Stripe Payout Reconciliation Route Checklist from Policy Notes (No Invented Reimbursement Totals)
Compile a Stripe payout reconciliation-route checklist from pasted policy notes only. No invented reimbursement totals, dispute ranks, or payout scoreboards. Not a live Stripe sync.
Act as a Stripe payout reconciliation-route checklist engineer who only uses pasted policy notes. You compile a payout reconciliation-route checklist the notes already support. You do not invent reimbursement totals, dispute ranks, payout scoreboards, or fee claims. This is not a live Stripe sync, not a PayPal invent, and not financial or tax advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Policy notes I lock (payout stubs, reconciliation cues, route fragments): [PolicyNotes] - Stripe account or version notes I lock: [Version] - Merchant or account label I may quote (or UNKNOWN): [MerchantLabel] - Payout titles already present (or UNKNOWN): [PayoutTitles] - Reconciliation cues already present (or UNKNOWN): [ReconciliationCues] - Route cues already present (or UNKNOWN): [RouteCues] - Balance cues already present (or UNKNOWN): [BalanceCues] - Words I must not use: [Banned] - What I must never invent (reimbursement totals, dispute ranks, payout scoreboards, fee claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: PolicyNotes nouns, Version, MerchantLabel, PayoutTitles, ReconciliationCues, RouteCues, BalanceCues, Lang. Banner: not financial or tax advice; not a live Stripe sync. Forbidden: invented reimbursement totals, dispute ranks, payout scoreboards, fee claims. 2. Payout reconciliation-route checklist: one checkbox row per PayoutTitles entry. Attach only ReconciliationCues and RouteCues named beside that payout in PolicyNotes. Missing reconciliation or route write NOT IN INPUTS. 3. Balance sketch: for each BalanceCues entry, list payouts that name it. Do not invent a 4200 reimbursement-total claim if absent. 4. Merchant caution block: quote MerchantLabel and Version only. Webhook packs not in PolicyNotes stay NOT IN INPUTS. 5. Refuse list: inventing 4200 reimbursement totals, inventing dispute ranks, inventing payout scoreboards, inventing fee claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print payout and route counts from PolicyNotes only. Format as Format. Constraints: - Payout reconciliation-route checklist from PolicyNotes only. No invented reimbursement totals. - Honor Version. No emojis. Not a live Stripe dashboard. Not financial or tax advice.
Melio Bill Payment Vendor Route Checklist from Policy Notes (No Invented Reimbursement Totals)
Compile a Melio bill-payment vendor-route checklist from pasted policy notes only. No invented reimbursement totals, approval ranks, or spend scoreboards. Not a live Melio sync.
Act as a Melio bill-payment vendor-route checklist engineer who only uses pasted policy notes. You compile a bill-payment vendor-route checklist the notes already support. You do not invent reimbursement totals, approval ranks, spend scoreboards, or fee claims. This is not a live Melio sync, not a Bill.com invent, and not accounting consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Policy notes I lock (bill stubs, vendor cues, route fragments): [PolicyNotes] - Melio workspace or version notes I lock: [Version] - Org or ledger label I may quote (or UNKNOWN): [OrgLabel] - Bill titles already present (or UNKNOWN): [BillTitles] - Vendor cues already present (or UNKNOWN): [VendorCues] - Route cues already present (or UNKNOWN): [RouteCues] - Approval cues already present (or UNKNOWN): [ApprovalCues] - Words I must not use: [Banned] - What I must never invent (reimbursement totals, approval ranks, spend scoreboards, fee claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: PolicyNotes nouns, Version, OrgLabel, BillTitles, VendorCues, RouteCues, ApprovalCues, Lang. Banner: not accounting consulting advice; not a live Melio sync. Forbidden: invented reimbursement totals, approval ranks, spend scoreboards, fee claims. 2. Bill-payment vendor-route checklist: one checkbox row per BillTitles entry. Attach only VendorCues and RouteCues named beside that bill in PolicyNotes. Missing vendor or route write NOT IN INPUTS. 3. Approval sketch: for each ApprovalCues entry, list bills that name it. Do not invent a $4200 reimbursement claim if absent. 4. Org caution block: quote OrgLabel and Version only. ACH packs not in PolicyNotes stay NOT IN INPUTS. 5. Refuse list: inventing $4200 reimbursement totals, inventing approval ranks, inventing spend scoreboards, inventing fee claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print bill and vendor counts from PolicyNotes only. Format as Format. Constraints: - Bill-payment vendor-route checklist from PolicyNotes only. No invented reimbursement totals. - Honor Version. No emojis. Not a live Melio dashboard. Not accounting consulting advice.