Kitchen management & food costing

Cooking the Books Virtual Assistant: a VA who keeps every recipe card costed to this week's prices

For venue owners, head chefs and caterers who bought Cooking the Books to control food cost, then discovered the invoice pile and the stocktake still need a human every single week.

30 minutes with Jenn, the founder. No card, no lock-in.

What your VA actually does inside Cooking the Books

Invoice Ripper queue

Supplier invoices emailed or snapped into Cooking the Books get extracted line by line by the Invoice Ripper; your VA reviews each extraction, matches new products to the right ingredient, fixes unit-size mismatches (the 2L that scanned as a 20L), and approves the batch so on-paper ingredient costs match what your suppliers charged this week, not last quarter.

Recipe cards and costing

Costed recipe cards kept honest: when an approved invoice moves an ingredient price, the VA opens the recipes it feeds, checks yields and portion counts still reflect how the kitchen makes the dish, and updates method photos, allergen fields and plating notes so the card is a document your chefs use rather than a relic from the menu launch.

Margin and price-change alerts

Working the price-movement alerts: which supplier lifted what, which dishes that flows into, and which menu items have drifted under your target gross profit. The VA turns the raw alert into a short weekly note naming the dishes and the dollars, so re-pricing is a five-minute decision instead of a quarterly archaeology dig.

Stocktake entry and variance

Your team counts the coolroom, dry store and bar; the VA keys the counts into the stocktake module, values the count at current invoice prices, and works the variance report so wastage, over-portioning or a receiving problem shows up as a named number in dollars, not a bad feeling about the meat order.

Supplier ordering admin

Orders built from your order guides and pars in the ordering module, sent to suppliers on their cutoffs, and checked back against what the Invoice Ripper says arrived, so short deliveries and substitutions get queried while the credit window is still open.

Menu engineering reports

With sales data flowing in from an integrated POS like OrderMate or Impos, the VA runs the menu engineering reports on a set cadence: sales mix against gross profit per dish, the quiet items dragging the menu, the high-margin items nobody is selling, delivered as a one-page summary before your menu meeting.

Accounts handover to MYOB or Xero

Approved supplier invoices pushed through the MYOB or Xero integration with the coding your bookkeeper expects, failed syncs chased, and the accounts-payable pile turned from a shoebox of dockets into a clean feed your accountant stops complaining about.

Cooking the Books gets bought in a moment of resolve, usually after a stocktake that showed food cost three points over budget, and for a month it gets fed. Invoices go in, recipes get costed, the numbers look sharp. Then service takes over, the invoice queue quietly climbs into the hundreds, the recipe cards freeze at launch-week prices, and the platform that was supposed to control food cost becomes one more subscription describing a system nobody has time to run.

That is not a software problem. Cooking the Books, built in Australia by CTB and Co (you may still know the company by the product’s own name, before the corporate rebrand), does exactly what it promises: the Invoice Ripper pulls supplier invoices apart line by line, the recipe builder holds costed cards with margins attached, the stocktake module values a count at live prices, and the POS and accounting integrations move data where it needs to go. What it cannot supply is the eight to twelve hours a week of disciplined human attention that keeps all of that true. That is the job a VA takes.

The daily rhythm a VA runs in your Cooking the Books

Start with the Invoice Ripper, because everything else in the platform is only as good as what comes out of it. Yesterday’s supplier invoices, emailed in or photographed at the loading dock, are sitting ripped and waiting for review. Your VA works through the queue: each extracted line checked against the document, new supplier product codes matched to the right ingredient, and the classic traps caught before they do damage. A carton that scanned at the wrong pack size will happily tell your recipes that cream costs a tenth of what it does. Once the batch is clean, it is approved, and every ingredient price in the system now reflects this week’s market, not the week you set the menu.

Price movement comes next. When an approved invoice lifts an ingredient, Cooking the Books knows which recipes that ingredient feeds, and your VA follows the thread: which dishes moved, which of them have slid under your target gross profit, and by how much. Instead of a dashboard you never open, you get a short weekly note in plain English. Chicken up nine percent, it hits the parma and the burger, the parma is now under 62 percent GP, here are the three options. The re-pricing call stays yours; the fact that you got to make it in week one instead of at the quarterly P&L review is the entire point.

Recipe cards get standing attention rather than heroic rescues. New dishes are built as proper costed cards with yields, portion counts, method steps and allergen fields filled in, and existing cards are corrected when the kitchen changes how a dish is made, because a card that says four portions when the kitchen plates five is quietly lying to your margins. If you cater, function menus get costed the same way before you quote, so the price on the proposal is built on today’s ingredient costs, not on what prawns cost last spring.

Stocktake is where most venues fall off the wagon, and it is the clearest place a VA changes behaviour. Your team still does the physical count, walking the coolroom and dry store with count sheets. Everything after that leaves the building: the VA keys the counts into the stocktake module, the platform values the count at current invoice prices, and the variance report gets worked line by line. Theoretical use against counted stock, gaps chased down to wastage, over-portioning or a receiving problem, and the result delivered as a named dollar figure. Stocktakes stop being the job everyone dreads and skips, because the dreadful half of the job now belongs to someone whose calendar it is on.

Ordering rounds out the loop. Orders are built from your order guides and par levels in the ordering module and sent before each supplier’s cutoff, then reconciled against what the Invoice Ripper says was delivered. Short deliveries and sneaky substitutions get queried with the supplier while a credit is still gettable, which on its own tends to claw back more than a rounding error each month.

And where your POS is connected, OrderMate and Impos being the common Australian pairings, sales data meets cost data and the menu engineering reports become worth running. Your VA pulls them on a set cadence: sales mix against per-dish gross profit, the popular-but-thin items, the high-margin dishes hiding in the corner of the menu, summarised to one page before your menu meeting. The data entry behind good menu engineering is unglamorous, which is exactly why it never happened when it was your job at 11pm.

At the back end, approved invoices flow through the MYOB or Xero integration with consistent coding, the VA chases anything that fails to sync, and your bookkeeper receives a clean accounts payable feed instead of a shoebox. If the same VA also handles your broader Xero housekeeping or expense categorisation, the whole paper trail from loading dock to P&L runs through one set of hands.

The honest bit

Some plain truths, because a costing platform is a place where optimism gets expensive.

The Invoice Ripper is capture, not judgement. It reads invoices impressively well, but it cannot know that a supplier renamed a product, that the 10kg listing is really the 5kg you always buy, or that the delivery was two cartons short. Every ripped invoice still needs a human review before approval, and if nobody does that review, the automation feeds bad numbers into every recipe it touches. This is the single biggest reason venues churn off the platform, and it is a staffing gap, not a software one.

Costing is only as honest as the yields behind it. If your recipe card says the rump yields 82 percent and your butcher section gets 74, no amount of invoice processing fixes the margin math. A VA maintains the cards and flags the suspicious ones, but the kitchen has to tell the truth about portions and trim, and that conversation is a chef’s to have.

The platform will not negotiate with a supplier, will not physically count a shelf, and will not decide what the parma should cost. It surfaces the numbers with unusual clarity. The moves are still yours.

And on candidates: because Cooking the Books is a specialist Australian product, we will be upfront on the discovery call if the strongest available VA has deep invoice-processing and costing experience rather than direct Cooking the Books hours. The supervised first week exists precisely so that gap closes inside your account, on your data, before anything runs solo.

What stays with you

Menu prices and every re-pricing decision, which suppliers you use and the terms you strike with them, authorising any payment (the VA prepares accounts payable, never releases money), your target gross-profit settings, the MYOB or Xero integration setup and account mapping, and anything that touches food safety: allergen declarations on recipe cards are entered by the VA but signed off by the chef who owns the dish, because a wrong allergen field is not an admin error, it is a safety one. The VA runs the machinery of food-cost control inside the modules you have scoped for them. The commercial and kitchen judgement wrapped around it does not leave your building.

What it costs and where to start

Cooking the Books admin lands on DotVA’s admin tier at $12-17 AUD an hour excl GST. A single venue keeping the invoice queue clear, recipes current, stocktakes entered and the weekly margin note flowing typically uses 10-15 hours a week, which works out around $500-1,100 a month; multi-site groups and busy caterers scale up from there. Getting a VA placed takes 7-10 business days end to end, and the first 5-7 days of work happen supervised inside your own Cooking the Books account, starting on the Invoice Ripper queue, with nothing running solo until you have signed off. There is a 30-day recalibrate-or-replace guarantee behind the match, a $500 refundable deposit that credits against your first month, and no contract holding you past 14 days notice.

For the wider picture of what a VA does across a venue, front of house included, read the hospitality virtual assistant page, and the VA cost guide breaks down the full pricing model. When you are ready, book a discovery call: Jenn runs every one personally, has put 87+ VAs into Australian businesses since 2024, and will say so plainly if your volume does not justify one yet. Come with your current Invoice Ripper queue count and your last completed stocktake date. Those two numbers usually make the case one way or the other.

Cooking the Books VA questions

Will the VA already know Cooking the Books, or am I training them from nothing?

Straight answer: Cooking the Books is a specialist Australian platform, so a candidate with direct hours in it is rarer than one who knows a big POS or Xero. Where we can find that person, we will, but the more usual match is a VA strong on supplier invoice processing, food or product costing and accounts-payable workflows, who learns your Cooking the Books setup during the supervised week. The transferable skill is the discipline of line-by-line invoice review and clean data entry, not knowing where the buttons live. They spend 5-7 days supervised inside your account, starting on the Invoice Ripper queue, before you approve any solo work.

Doesn't the Invoice Ripper already automate the invoices? Why would I need a person?

The Invoice Ripper does the extraction, and it does it well, but extraction is not the finish line. Someone still has to review each ripped invoice, match a supplier's new product code to the right ingredient, catch the pack-size errors that would poison your recipe costs, approve the batch, and query the short delivery the invoice quietly reveals. Venues that skip that review end up with recipe cards costed off bad data, which is worse than no costing because you trust it. The VA is the review-and-approve layer that turns automated capture into numbers you can price a menu from.

Can a VA do our stocktake remotely?

The counting, no, obviously: someone in your venue still walks the coolroom, the dry store and the bar with a count sheet. What moves off your plate is everything after the count: keying the numbers into Cooking the Books' stocktake module, valuing the count at current prices, running the variance report and turning it into a plain-English note about where the gap is. Most venues find the data entry and variance chase was the reason stocktakes kept getting skipped; once that is someone's actual job, the monthly count starts happening on schedule.

What can the VA see in Cooking the Books, and what about our accounts?

Their login is scoped to the modules and venues you assign, so the working set is usually the Invoice Ripper, recipes, stocktakes and ordering. The MYOB or Xero connection pushes approved invoices across, and the VA watches that feed and chases failures, but the integration settings, chart-of-accounts mapping and anything to do with paying suppliers stay with you and your bookkeeper. A VA preparing accounts payable is not a VA authorising payments; that line does not move.

What does a Cooking the Books virtual assistant cost?

This work sits on the DotVA admin tier at $12-17 AUD an hour excl GST, and most single venues need 10-15 hours a week, roughly $500-1,100 a month, to keep the invoice queue at zero, recipes current, stocktakes entered and the margin note landing weekly. Multi-site groups and caterers with heavy function volume run more. A $500 deposit, refunded or credited to your first month, gets the placement moving, and you can step away with 14 days notice.

Ready to hand it over?

Book a free discovery call

30 minutes with me, the founder. Tell me you run Cooking the Books and what's eating your week, and I'll tell you honestly what a VA can own inside it, what it costs, and whether it makes sense.

1. Tell us what Cooking the Books work to take off your plate. 2. Pick a call time that suits. 3. Meet your shortlist of 3-5 matched VAs, usually inside 7-10 business days.

87+ Australian placements since 2024, a 30-day replacement guarantee and no lock-in beyond 14 days notice. Audit the 5-stage vetting process and how VA access is secured before you book.

No obligation. No credit card. Jenn, the founder, reads every enquiry herself and replies inside one business day. Prefer to talk first? Call (03) 9961 6076, Melbourne line, business hours. DotVA is Boring Ventures Pty Ltd, ABN 67 671 943 758, Melbourne. How to verify us.

Not ready for a call? Get an instant cost estimate (2 minutes, no email needed) or check if you are ready in 90 seconds.

VAs for other software & platforms