Singapore F&B Supplier Invoice GST and UEN Workflow

A Singapore F&B supplier invoice GST workflow should capture the supplier name, UEN or GST registration number, invoice number, invoice date, full or simplified tax-invoice status, GST-exclusive amount, GST amount, GST-inclusive total, and line-item categories. For beverage suppliers, Beverage Container Return Scheme deposits need their own non-GST field or row so they do not inflate input GST or food and beverage COGS.

That is the practical answer behind the paperwork. A restaurant, cafe, bar, or central kitchen is not just trying to turn invoices into text. The bookkeeping file has to support supplier payments, input-tax review, outlet-level spend checks, and the quarterly GST F5. If the extraction collapses the GST line into the total, loses the supplier's UEN, or treats a refundable beverage-container deposit as taxable stock, the cleanup moves straight into month-end.

The document mix is also messier than a standard AP queue. A Singapore F&B operator may have monthly statements from foodservice distributors, line-item invoices from produce suppliers, cash-and-carry receipts, delivery notes, mobile photos from a store manager, and beverage invoices with deposit lines. Some documents are full tax invoices. Some are simplified tax invoices. Some are receipts that still need to be coded for spend review even if they are not enough on their own for a GST input-tax claim.

The purchase log therefore needs to do two jobs at once. It must preserve the statutory fields a bookkeeper checks before claiming input GST, and it must preserve the operating fields a restaurant uses to understand food, beverage, packaging, cleaning, and delivery costs. The useful output is not a generic vendor-date-total spreadsheet. It is a GST-aware supplier file with enough source detail that a reviewer can trace each row back to the original PDF, scan, or photo.

Separate statutory tax-invoice fields from kitchen operating fields

The cleanest schema splits the extraction into two groups: fields that support Singapore GST review, and fields that help the kitchen or finance team understand what was bought.

The statutory side should include supplier legal name, supplier address where available, UEN, GST registration number, invoice number, invoice date, customer name or outlet identifier, document type, tax-invoice status, GST rate, GST-exclusive amount, GST amount, and GST-inclusive total. If the invoice has a page count, statement reference, delivery order number, or credit-note marker, capture that as well. Those fields make later review faster because the bookkeeper does not have to reopen the PDF just to answer whether the invoice can support an input-tax claim.

The operating side should describe the purchase. For a Singapore cafe supplier invoice Excel file, useful columns include supplier category, line description, SKU or product code, quantity, unit of measure, unit price, delivery date, outlet, expense category, and COGS or non-COGS classification. A seafood delivery may need quantity and weight. A dry-goods invoice may need carton counts and product codes. A cleaning-supply invoice belongs in operating expenses, not food cost, even if it arrives from the same broad supplier group as other kitchen consumables.

Map the invoice anatomy directly into columns. Header identity becomes supplier legal name, trading name, UEN, GST registration number, invoice number, date, and customer or outlet. The totals box becomes GST-exclusive amount, GST amount, GST rate, GST-inclusive total, and rounding adjustment where shown. The line table becomes description, quantity, unit, unit price, line total, category, and COGS flag. A BCRS line becomes a separate deposit amount and GST treatment field. The file metadata becomes source file, source page, and extraction note.

The row design depends on the review task. One row per invoice is enough for basic payment approval and GST total checks. One row per line item is better for food-cost analysis, beverage-cost review, packaging spend, and vendor price checks. For supplier statements, the output may need one row per listed invoice or credit note, with a separate source reference back to the statement page.

This is where invoice data extraction for supplier invoices fits the workflow: Invoice Data Extraction lets a user upload PDFs or images, describe the exact fields and row structure in a prompt, and download the result as Excel, CSV, or JSON. For this use case, the prompt should name the Singapore fields explicitly and ask for source file and page references on every row.

Treat full and simplified tax invoices as extraction states, not filing theory

In Singapore, a simplified tax invoice can be used when the total amount payable including GST does not exceed S$1,000. Above that, the supplier invoice needs the fuller tax-invoice detail a GST-registered customer keeps as support for input tax. A restaurant purchase log should capture that distinction as a document status, not leave it for someone to infer later from the total.

The extraction rule is straightforward: classify the document as a full tax invoice, simplified tax invoice, receipt, credit note, supplier statement, or delivery note, then capture the fields the document actually contains. A simplified tax invoice may have the supplier's name, address, GST registration number, date, invoice number, description, GST-inclusive total, and wording that the price includes GST. It may not identify the customer in the same way a full tax invoice does. A full tax invoice should carry fuller detail, including the supplier identity, invoice identifier, invoice date, description of goods or services, GST rate, GST-exclusive amount, GST amount, and GST-inclusive total.

For a restaurant or cafe, this matters because low-value paperwork is common. A team might have cash-and-carry receipts for emergency ingredients, small packaging purchases, or one-off maintenance supplies that sit below the simplified threshold. Mainstream foodservice, beverage, seafood, linen, and equipment suppliers are more likely to issue full tax invoices, especially for weekly or monthly account billing.

The extraction output should not reject simplified documents just because they have fewer fields. It should mark the status clearly, populate the available fields, and leave review columns where the bookkeeper can decide whether the document is enough for the intended treatment. For the fuller compliance treatment, including required fields and related Singapore GST invoice rules, use the dedicated guide to Singapore GST tax invoice requirements.

Verify the supplier identity before claiming input GST

UEN is not a decorative registration detail. In a Singapore supplier file, it is part of the identity chain that connects the invoice header, supplier master record, GST registration number, payment record, and input-tax review. If the purchase log captures only a trading name, the bookkeeper may not notice that two similar supplier names belong to different entities or that a GST claim is being made from a document without the right registration detail.

The schema should allow separate columns for supplier legal name, trading name, UEN, GST registration number, and invoice source. In many cases the UEN and GST registration number appear the same. In other cases, the invoice may show a GST registration number in a different format from the company UEN. Forcing both into one field creates avoidable ambiguity, especially when suppliers have group structures, branch names, or related entities.

Verification is an AP control, not a one-time setup task. Before relying on an invoice for input GST, compare the supplier name and UEN or GST registration number on the invoice with the supplier master file and ACRA's UEN lookup. Capture legal name, trading name, UEN, and GST registration number separately before deciding whether the invoice supports input tax. The same control should apply when a vendor changes its billing entity, a new outlet starts buying from a local supplier, or an invoice image is cropped so the header is incomplete.

F&B has a recurring set of supplier categories where this matters: produce, seafood, dry goods, beverage distributors, packaging, cleaning chemicals, equipment servicing, and maintenance contractors. Red flags include inconsistent supplier names across invoices, missing GST registration numbers where GST is charged, handwritten corrections to the supplier header, reused receipts from another outlet, and mobile photos that cut off the top of the document. Capturing the source file and page number beside the extracted UEN makes those exceptions much easier to review.

Keep BCRS beverage deposits out of GST and COGS

BCRS is the new line item Singapore beverage-heavy operators cannot afford to treat casually. IRAS guidance on GST and BCRS deposits states that Singapore's Beverage Container Return Scheme starts on 1 Apr 2026, uses a 10-cent refundable deposit on each regulated beverage sold, and that the BCRS deposit is not subject to GST.

That fact changes the extraction design. A beverage invoice should not roll the deposit into taxable beverage cost, and the GST calculation should not apply 9% to the deposit. The output needs a separate BCRS deposit amount, and, where the supplier shows it, a container count or product-level reference that explains how the deposit total was calculated. If the invoice has both beverage goods and BCRS deposits, those components should land in different columns or rows.

At a bookkeeping level, the beverage product cost belongs in COGS, and the GST on the taxable beverage supply may be input tax if the usual conditions are met. The refundable BCRS deposit is different. Post it to a separate non-GST, non-COGS deposit or clearing account pending refund, credit, or settlement. Treating it as beverage cost overstates COGS. Treating it as taxable overstates input GST.

The common extraction mistakes are predictable: the deposit disappears into the line total, the model calculates GST on it, the container count is lost, or a later supplier credit is netted against the wrong purchase category. Those mistakes become harder to find when beverage suppliers issue long invoices covering bottled water, canned drinks, mixers, beer, soft drinks, and return adjustments on the same statement.

The safest purchase-log design gives BCRS its own fields: deposit amount, GST treatment, container count where available, related product line, supplier credit reference, and source page. The reviewer can then see, without reopening every invoice, which amount is beverage cost, which amount is GST, and which amount is a refundable deposit movement.

Reconcile 9% GST and service charge without mixing sales and purchases

Singapore's current GST rate is 9%, and the invoice date matters because the rate moved from 7% to 8% on 1 Jan 2023, then from 8% to 9% on 1 Jan 2024. A supplier invoice dated in the current period should not be checked with an old rate, and an older invoice should not be forced into the current-rate logic just because it appears in today's catch-up batch.

Supplier invoices and customer bills also sit on different sides of the GST return. Supplier invoices support input tax, if the document and purchase meet the claim conditions. Customer bills create output tax. A restaurant spreadsheet that mixes both without clear labels invites mistakes, especially when the same outlet manager sends supplier receipts, POS summaries, and customer event invoices in one folder.

The F&B service-charge calculation belongs on the sales side, but operators often think about it alongside supplier GST because both affect daily paperwork. A typical dine-in bill with S$100 of food and beverage plus a 10% service charge has a S$110 subtotal. GST at 9% is calculated on S$110, giving S$9.90 of GST and a S$119.90 total. The service charge is subject to GST because it forms part of the price for the goods and services supplied.

That does not mean service-charge logic belongs in the supplier purchase log. It belongs in POS reconciliation, event billing, or sales audit workpapers. The supplier-invoice workflow should stay focused on input-tax support: invoice date, GST rate, GST-exclusive amount, GST amount, GST-inclusive total, document status, and source reference. If the same extraction batch contains sales and purchase documents, include a document-type column and separate the outputs before review.

Design the weekly purchase log around how F&B buys

A Singapore restaurant supplier invoice bookkeeping file should reflect how the business actually buys. Food, beverage, packaging, cleaning, linen, smallwares, repairs, delivery charges, and outlet transfers do not behave the same way in review. A useful purchase log makes those differences visible instead of burying them under broad supplier names.

For food and beverage, line-item detail is usually worth the extra structure. It lets the bookkeeper and operator see price changes, product substitutions, quantity movements, and category shifts across the week. Invoice-level totals may be enough for simple AP posting, but they are thin for COGS review because they hide whether the spend was produce, seafood, meat, dairy, dry goods, bottled drinks, alcohol, disposables, or delivery. The same logic behind foodservice wholesaler invoice purchase logs applies in Singapore, with extra care for GST, UEN, and BCRS fields.

Supplier statements need their own treatment. A monthly statement is not the same as an invoice, but it is useful for reconciliation. The extracted rows should show each listed invoice number, date, amount, credit note, payment, and outstanding balance, then point back to the source statement page. When the statement total does not agree to the invoice folder, the reviewer can identify the missing document instead of scanning the full supplier PDF manually.

Categories should be practical enough for restaurant review and disciplined enough for accounts. Produce, seafood, meat, dry goods, beverages, packaging, cleaning, repairs, and freight are more useful review labels than a single purchases bucket. For posting, the category can map into the chart of accounts. For management review, it can support menu costing, outlet comparison, supplier negotiation, and variance checks. The same principles used in restaurant supplier invoice coding become more useful when the row also carries Singapore GST and supplier-identity fields.

Invoice Data Extraction can preserve source file and page references on each output row, which matters when a bookkeeper traces a purchase-log line back to the original supplier invoice, delivery note, or statement. It can also process mixed PDFs and image files in batches, filter irrelevant pages, and output the result in spreadsheet form for review. Imported ingredients should still have their own document trail, because import GST and customs permits may sit outside the domestic supplier invoice.

Use InvoiceNow where it exists, and keep extraction for the supplier long tail

InvoiceNow and Peppol change the direction of travel for Singapore B2B invoicing. When both trading parties are onboarded, invoice data can move in structured form rather than arriving as a PDF attachment or phone photo. For a restaurant group with larger suppliers, that can reduce the amount of manual capture in the AP process.

It does not remove the supplier-invoice workflow. F&B still has a long tail of smaller vendors, cash-and-carry receipts, market purchases, imported-item paperwork, ad hoc repairs, mobile photos, and mixed statements. Some suppliers will be onboarded early. Others will keep sending PDFs, scanned invoices, receipts, or WhatsApp images for years. A realistic process accepts structured e-invoices where they exist and keeps an extraction workflow for everything else.

The operating model should be consistent across both sources. Use the same purchase-log schema for supplier identity, UEN or GST registration number, invoice date, invoice number, document status, GST totals, BCRS deposits, line categories, outlet tags, and source references. Structured e-invoices can populate that schema directly. PDFs, scans, and images can be extracted into the same columns so the bookkeeper reviews one coherent file rather than several partial ledgers.

Invoice Data Extraction is the extraction side of that mixed workflow. Users can upload PDF, JPG, and PNG supplier documents, prompt for the Singapore F&B fields they need, and download Excel, CSV, or JSON output. The discipline is to define the fields once, keep GST and BCRS treatment explicit, and make the resulting data usable for F5 preparation, supplier-spend review, and month-end close.