Invoicing software covering place of supply, electronic invoices, transport documents and reconciliation with your books
Tax rules move into the billing screen. The software picks the right sales tax or VAT treatment from the delivery location, obtains the e-invoice reference where a tax authority requires one, and links credit notes to invoices. Your accountant still files the returns.
- Rules agreed with the accountant before building
- Each rule traces to a checkable document
- Invoicing is ours, returns are the accountant’s
This work covers distributors billing across regions, manufacturers moving goods under transport documents, service companies with reverse charge purchases and exporters raising invoices without tax. E-commerce brands with returns fit too. The tax rate is rarely the trouble. It is the delivery location on a branch shipment, an item master with no tax classification code, or a sales register that differs from the accounting software at month-end. Because rules differ by market, we ask your accountant to check the setup against local requirements.
Where tax invoicing needs correction afterwards
Cross-region sales taxed as local
The customer master holds one address. The goods, though, go to the buyer’s branch in another region and the software still taxes them like a local sale, so the buyer rejects it. A credit note and a re-issue follow.
Items in the master without tax codes
The classification field is blank. Nothing forces it, so products enter the item master without codes, invoices for them are printed and sent, and the gap surfaces when the sales return is prepared.
Transport documents raised on a separate portal
Everything is typed twice. Billing prints the invoice, then someone keys the same details into an authority’s system, where invoice numbers drift and a vehicle digit goes wrong. The truck at the checkpoint pays.
Sales register and accounting software disagree
Two totals, one month. Billing shows one figure and the accounting software another. The gap traces back to rounding, a cancelled invoice that was never reversed, or a credit note posted against nothing. Someone hunts for it every month-end.
Returns handled by editing the invoice
The original bill gets edited. Goods come back, no credit note exists, and the invoice series now has a hole, so rebuilding what was actually supplied that month turns into slow guesswork.
Advances recorded as plain payments
Advance receipts get keyed in as ordinary payments. Nobody works out the tax treatment of money received before the supply until someone reads a bank statement months later and the period may already be filed.
Invoice formats with missing fields
An old template makes a poor invoice. It may lack the delivery location, the reverse charge indicator or the right series prefix, and a buyer’s accountant may query it before claiming input tax. It still looks like a bill.
Correct tax invoicing depends less on knowing the rates than on applying the right rule at the moment of billing. The same numbers must reach both the tax authority’s system and the accounting software. No document should leave with a field missing.
Rules applied at billing instead of corrected afterwards
Work starts with the client’s real transaction types. The accountant reviews each one. The rules then sit inside invoicing: how tax is decided, which series applies, what a document must hold before saving, and when an e-invoice or transport document falls due. Calls to authority systems run from the invoice record itself. The same figures post to the accounting software.
Place of supply decides the tax
The delivery location decides. Ship-to place, supply type and registration choose the tax treatment, so a branch delivery in another region is never taxed like a counter sale.
One record, one set of numbers
One record does three jobs. The invoice that prints is the one sent for its e-invoice reference where required and the one posted to the books, so nothing is typed a second time.
Validation before the document exists
Bad entries stop at the save button. A missing tax code, a tax registration number that fails its check, a blank delivery location or an unpriced line blocks the save. Fixing an entry beats issuing a credit note.
What changes when invoicing is engineered
What the business gets, before any talk of technology.
Tax taken from the ship-to position
Tax follows the ship-to position. Cross-region and local deliveries to the same customer separate at entry instead of at correction, and the accountant signs off the rules before they go live.
e-Invoice and transport document from one record
Numbers are carried over, never retyped. The e-invoice reference, QR code and transport document come from the record that produced the invoice, and responses are stored against that invoice for any later audit.
Incomplete documents stopped at entry
Gaps are caught while the entry is open. Missing codes, failed registration number checks and empty delivery locations are flagged on screen, and staff settle each one before the document is issued.
Sales register compared with the books
Totals are compared every day. Ledger-wise and tax-wise figures from billing are set against the accounting software. Any gap that appears carries a stated reason such as a rounding rule or an unposted cancellation.
Credit notes linked to the original invoice
The series stays unbroken. Returns and rate corrections produce documents raised against the original invoice, so the whole month can be rebuilt from stored records without anyone guessing.
Data prepared for the accountant
The accountant gets a work list. Extracts arrive in the layout the sales and purchase returns need, with exceptions listed apart, so nobody works from raw billing exports.
What tax and e-invoice engineering includes
Everything from the first discovery session to production and long-term upkeep.
Transaction mapping with your accountant
Every supply type is written down. Local, cross-region, branch transfer, subcontracted work, export, reverse charge and exempt purchases are each settled, and the accountant confirms every treatment first.
Tax determination logic
Software decides the tax treatment. Rules inside it choose the rate and tax type from delivery location, registration and supply type, so the choice no longer rests with the billing clerk.
Invoice format and mandatory fields
One template is never enough. Tax invoice, simple bill, delivery note, debit note and credit note each get a print format carrying every field the document needs. Nobody edits a template by hand.
Item and party master cleanup
Masters get cleaned first. Tax classification codes are filled, validated and tied to rates, tax registration numbers are checked where a public lookup exists, and addresses are split so region becomes its own field.
e-Invoice registration and reference handling
Registration happens on save where a tax authority requires it. The invoice goes to the authority’s system, and the reference and signed QR code are stored against the record and printed on the bill. Cancellation stays inside the allowed window.
Transport document generation and updates
Dispatch data is captured once. Documents are raised from the same invoice with carrier, vehicle and distance entered at dispatch, and vehicle changes, extensions and cancellations are handled.
Document series and numbering control
Numbers never skip or repeat. Series run apart for each branch, document type and financial year, and a cancelled document is recorded instead of deleted, so a repeated or missing number shows up.
Credit and debit note workflow
A return becomes a document. Returns, rate differences and post-supply discounts turn into linked notes raised against the original invoice, with the reason recorded and the stock effect posted in the same step.
Accounting software integration
Your accounting software receives clean postings. Sales, purchases and tax entries land in the right ledgers with a daily reconciliation report beside them, which replaces a bulk upload nobody checks.
Purchase and input tax matching
Input tax gaps surface early. Vendor bills are recorded with registration number, invoice number and tax split, then compared with the data the accountant downloads, so missing credits can be raised with the vendor.
Return preparation extracts
Returns start from tidy data. Sales and purchase extracts follow the layout the returns need, and unmatched items and exceptions are listed apart for the accountant to work through.
Rate and rule change updates
Tax rules keep changing. When rates, schemas, thresholds or authority specifications move, we update the configuration and identify every affected document, so the fix lands before the next filing cycle.
Where tax and e-invoice engineering is used
The processes this service is most often asked to set up and automate.
Distributor delivering to a branch in another region
The dealer is registered in one region. Delivery goes to a branch in another, so the software reads the ship-to place instead of the billing address, applies the cross-region tax rule and obtains the e-invoice reference. The transport document comes next. Loading bay staff capture the vehicle.
Manufacturer sending subcontracted work out and receiving it back
Material goes to a subcontractor for plating. Delivery notes are raised for both legs with the correct document type, and transport documents follow where consignment value crosses the local limit. Stock stays visible as lying with the processor.
E-commerce brand handling product returns
Every return becomes a credit note. It links to the original invoice and the return reason, the stock movement is posted together with it, and the series stays intact. Monthly marketplace reconciliation uses those links.
Service company with reverse charge on goods transport
Freight bills may attract reverse charge. Purchase entry flags it at the moment of booking, raises the self-invoice where needed and lists it, so the accountant receives a clean list each month.
Building material supplier dispatching by truck
Trucks leave with valid paperwork. The invoice is raised in billing, the transport document is created from the same record, and the gate captures the vehicle number on a phone. A vehicle change triggers an update.
Small retailer where accounting software alone is enough
A single-counter shop bills locally. It sits below any e-invoicing limit and its accountant manages in the accounting software, so custom invoicing would only add cost without adding value. Clean the item master, fix the print format.
Is this the right service for you?
It suits businesses that have outgrown manual processes and want a system they can rely on.
Businesses billing across regions
Place of supply is a live decision. On most invoices a wrong call means a credit note, a re-issue and a buyer’s accountant asking why the document changed again.
Companies moving goods under transport documents
Dispatch is the hard part. Distributors, manufacturers and suppliers deal with carriers, mid-route vehicle changes and consignments in transit, and each stage needs a valid document behind it where the rules ask for one.
Businesses crossing an e-invoicing threshold
The e-invoicing limit can move. A tax authority may set a turnover threshold, so a business outside it one year can fall inside later while running software never built for electronic invoices.
Anyone building or replacing billing software
Design the tax logic first. A new ERP, portal or e-commerce system that will raise invoices needs its rules agreed with an accountant at the start, because patching later costs more.
Businesses whose books do not reconcile
Reconciliation is a monthly fight. The sales register and the accounting software disagree, days go into hunting the difference, and the cause usually lies in how documents are created and not in the accounting itself.
When this work is not needed
Small shops may need none of this. Below any e-invoicing limit, with an accountant comfortable in the accounting software, cleaning the item master and fixing the print format may be the whole job. The same holds where the books are in order and the accountant has no open issues, so a review of recent invoices decides it.
What it can do, in plain terms.
Place of supply determination
Tax treatment comes from the ship-to place, the supply type and the registration status, so the billing address alone never settles it. That prevents a frequent cause of wrongly taxed cross-region sales.
Tax registration number validation
Registration checks run on every party. Structure and status are verified where a lookup exists when a party is created or edited, and the legal name and region are pulled back into the master record.
Tax classification enforcement
No code, no product. Classification codes and rates are mandatory at item creation, so nothing enters the master without the field the return will need later.
Multiple document types
Each document type has its own rules. Tax invoice, simple bill, delivery note, debit note, credit note and self-invoice carry separate formats, numbering and mandatory fields that are all checked before the document saves.
Controlled numbering series
Numbering has no gaps. Series run per branch, document type and financial year without gaps or repeats, and a cancelled number is recorded and never reused for a later document.
e-Invoice and signed QR handling
Every invoice that needs one carries a reference. The invoice is registered with the authority’s system, the signed response is stored against the record, and the QR code prints on the document.
Transport document integration
Documents come from the invoice. Vehicle updates, extensions and cancellations sit beside the carrier record on that same screen, so nobody has to open another portal in a separate tab.
Reverse charge flagging
Reverse charge is flagged at entry. Purchases and expenses that attract it are marked when booked, the self-invoice is raised, and the accountant gets the list instead of finding items at filing time.
Rounding and tolerance control
Rounding follows one rule. The same method applies across line totals, tax totals and invoice totals, because mixed rounding is a common source of month-end differences between billing and the books.
Accounting posting with reconciliation
A mismatch shows the next morning. Entries go to the correct ledgers, a daily comparison report sets billing against the books, and any difference arrives with the document that caused it.
Purchase register and credit matching
Purchases match against authority data. Vendor bills are captured with registration number, invoice number, date and tax split, so a comparison shows which credits are missing and who to chase.
Exception reporting
One list holds every exception. It covers invoices held, e-invoice references not obtained, transport documents nearing expiry, credit notes without a parent document and parties with invalid registrations.
How the work runs, step by step.
From the first conversation to a release your team uses every day. Each step says what you provide and what you get back.
- 01
Review with your accountant
Real documents come first. We review a few months of actual invoices and list every transaction type, using real documents rather than a description of how billing is meant to work. We need the accountant for a few sessions.
- 02
Rule book and document design
The rule book is signed off. Tax treatment per transaction type, document formats and validation rules are written down and approved, and everything else is built against that document. We need the accountant’s agreement in writing.
- 03
Master data cleanup
Masters get fixed before the build. Item codes, classification, rates, party registration numbers and addresses are corrected and validated, and an unclassified item needs someone from the product team to decide what it is. We need that person reachable.
- 04
Build and system integration
Authority systems get wired in. The invoicing logic is built and connected to any e-invoice and transport document services, and we need access credentials or an arrangement with a service provider. A test environment keeps live billing untouched.
- 05
Parallel billing and reconciliation
Old and new run side by side. Real invoices are raised both ways for an agreed period and the two registers are compared, so billing staff double-enter during that stretch and the accountant checks the comparison.
- 06
Go-live and the first filing cycle
Go-live is not the end. We stay through the first month-end and the first return preparation, and we need a named contact during filing week, since anything missed shows up then.
What you receive when the work is done.
Everything needed to run, maintain and extend the software without depending on us.
It connects to the systems you already use.
Tools that work stay. The new system is joined to them rather than replacing them.
Tax authority systems
- Electronic invoice services
- Transport document services
- Tax authority data downloads
- Approved service providers
Accounting software
- Your current accounting software
- Zoho Books
- Xero
- QuickBooks
- Sage
Business systems
- Custom ERP and billing software
- Odoo
- SAP Business One
- Dealer and distributor portals
- Point of sale systems
Commerce and payments
- Shopify and WooCommerce
- Marketplace settlement files
- Card and bank-transfer payment providers
- Wallet collections
Logistics
- Carrier portals
- Courier aggregator APIs
- Vehicle and driver capture on mobile
- Weighbridge records
Chosen for reliability and a long life.
Picked to match your scale and to stay maintainable for years.
Application
Authority integration
Accounting bridges
Documents
Reliability
Why owners choose GullySystem.
The accountant is involved from the start
The accountant sits in the room first. The rule book is agreed with the person who signs the returns before anything is built, because a developer’s reading of tax law is a risk.
The line is drawn at filing
Filing stays with your accountant or tax adviser. Our side is correct documents and clean data, while positions on the law, notices and representation before the tax authority remain with them.
Validation before the document exists
Bad entries stop at the counter. Missing codes, failed registration checks and blank delivery locations are caught before the customer leaves with the bill, because stopping a save is simpler than issuing a credit note.
Reconciliation built in
Differences appear next morning. A daily comparison between billing and the books lets the software find the gap overnight, so nobody discovers it while preparing the return in filing week.
Planning for outages
Outages do not stop billing. An authority’s system is unavailable at times, so invoices queue, retry and are tracked, and the counter keeps working while a list shows which documents await a reference.
Watching for rule changes
The rules never stand still. Rates, schemas and thresholds change, so we update the configuration and identify the documents affected, and the accountant does not stumble on the change while preparing a return.
How the engagement can be shaped.
Each model says what it suits and how the work is scoped. Pick the one that fits, or ask which one we would suggest.
Invoicing review
A business unsure whether its invoices, masters and returns agree can begin with a sample of recent documents, forming a defined scope of its own. A tax-aware engineer works beside your accountant, who is the contact and explains how each document is meant to be raised. Extra entities or periods are priced in a written note. It ends with a report on fixes.
e-Invoice and transport document integration
Fitting for a business that keeps its billing software and needs e-invoice registration and transport documents connected, itemised by document type and system. An integration engineer and a tester build the connection, retry queues and exception lists, and your accountant approves test invoices. A new document type is written up and costed before work starts. The exception procedure is handed over.
Invoicing built into a new system
Choose this for an ERP, portal or e-commerce build where tax must be right from the first invoice; the tax work sits inside the build’s phases. Developers and a tax-aware analyst design the logic, numbering and posting together, and your finance lead signs the rules. A rule change is priced before the build absorbs it. The rules stay with you.
Ongoing support and updates
It serves a business facing rate and specification updates in every filing cycle, paid by the month with cover at month-end and in filing week. The engineers who built the integration keep configuration current and review exceptions, and your accountant reports mismatches. Updates the portal forces are absorbed, while a new document type gets a separate note and price. Notice ends it.
Questions owners ask first.
Plain answers to the questions asked before work starts.
Do you file our tax returns?
No. Filing, positions taken on the law, notices and representation before the tax authority stay with your own accountant or tax adviser and are never handled by our engineers. Our work is the systems that feed the returns. That means invoices with the right tax and fields, e-invoice references obtained, transport documents raised, credit notes linked, and extracts with exceptions listed apart.
Does e-invoicing apply to our business?
It depends on the countries you trade in. Some tax authorities require electronic invoices above a turnover limit, and limits get revised over time. The software can be ready early.
How does e-invoicing actually work?
Where a tax authority requires it, the software sends invoice details to the authority’s system, which returns a reference number and a signed QR code for that exact document. Both are stored and printed. It is not a separate invoice. It is the same invoice, registered. Cancellation works only inside the window the authority allows, so after that the route is a credit note linked to the original invoice, raised with the reason recorded. Registration runs from the printing record.
What happens when the authority’s system is down?
Counter work does not stop. Invoices are created and queued, the system retries on its own, and a list shows which documents still wait for a reference. Staff see the state at a glance, and dispatch decisions are made with that status in view, so nobody dispatches goods unaware that registration is pending.
Can the transport document be raised from the same screen as the invoice?
Yes, both come from one record. The usual failure is an invoice from billing and a transport document typed separately into another system, after which the invoice number stops matching or a vehicle digit slips. Vehicle and carrier details can be captured on a phone at the loading bay, and the document is updated when the vehicle changes.
Our sales register never matches our accounting software. Why?
The tax rate is rarely the cause. Four causes are common. Rounding is applied differently at line level and invoice level, and cancelled invoices were removed from billing but never reversed in the books. Credit notes were posted with no link to the original document, while invoices created elsewhere, such as on a marketplace or at a branch, never reach the posting job. We compare one month document by document. A daily reconciliation follows.
Will this work with our accounting software, or do we have to replace it?
Yes, it works with most accounting software. The books stay where they are. The invoicing system raises the documents, handles the authority connections and posts entries into the right ledgers, with a reconciliation report each day. What changes is the direction of data. Entries flow from the operational system into the books. Nobody retypes them at day close.
How do you handle branch transfers and subcontracted work?
Each is its own transaction type. The accountant decides the documents for each. In some countries a stock transfer between the business’s own registrations counts as a supply, so it needs the right document and a transport document where the value crosses a limit. Material sent out for processing moves on one delivery note and returns on another, and stays visible in stock as lying with the processor.
What about reverse charge and export invoices?
Both are configured as distinct transaction types. Reverse charge purchases, such as freight from a transport agency, are flagged at entry so the self-invoice is raised without anyone having to remember. Exports can be raised without tax, or with tax where a refund is claimed, and shipping details travel on the document. The accountant picks the path. Both paths are implemented.
Can you fix our existing billing software rather than replace it?
Often, yes. Source and data model decide. Where the software is reasonably built and its source or database is reachable, tax determination, validation, authority integration and accounting posting can be added around it. Replacement becomes the route in three cases. The source is unavailable, the data model has no place for a region or a tax code, or the vendor cannot be reached. A review tells us which case applies.
What drives the cost of this work?
Scope and condition drive cost. One local sale type is simple. A business with cross-region sales, branch transfers, subcontracted work, exports, reverse charge purchases and e-commerce returns has several rule sets to encode and test. Other factors are whether the existing software can be modified, and whether the item and party masters are clean or need real repair first. Integrating both e-invoicing and transport documents adds work. So does cleaning reconciliation history. Cost is confirmed after scoping.
What happens when tax rates or rules change?
We update the configuration whenever rates or rules change. Rates change, schemas are revised, thresholds move and authorities publish new specifications, so a configuration that was right last year can quietly turn wrong. Under an ongoing support arrangement we test it against the revised specification and produce a list of affected documents and masters. Without support, a schema change can start rejecting invoices, which is why some continuing arrangement is recommended after go-live.
Does the software certify that our invoices are compliant?
No. The software applies the treatment your accountant has agreed in writing, refuses to create a document missing a field the format requires, and reconciles daily against the books. Each invoice traces back to the rule that produced it, so if a document is questioned the client can show how it was made and who approved the rule. The opinion belongs to your accountant, tax adviser or lawyer.
Read before you decide.
Practical notes on the questions this service raises, not product marketing.
IRN, QR Code and e-Way Bill: How Billing Software Handles Each
What the registration portal returns for an e-invoice, why the IRN and e-way bill should come from the billing record itself, and how outages are handled.
Why Your Sales Register Does Not Match Tally at Month-End
Rounding, cancelled bills never reversed, unlinked credit notes and invoices that skip the posting job. How to find which one is behind your month-end gap.
Fix Your Billing Software for GST or Replace It: How to Decide
When tax logic, portal links and Tally posting can be added around your billing software, when replacement is the route, and when neither is needed at all.
How place of supply decides CGST, SGST or IGST on an invoice
How ship-to state, supply type and registration decide whether an invoice carries CGST and SGST or IGST, and how billing software applies your CA’s ruling.
More guides on this page’s topic
- Crossing the e-invoicing limit: a setup plan for billing software
- What to ask a vendor before buying billing software for GST
- Why the portal rejects an invoice at IRN generation
- Tally alone or a billing system beside it: where the line falls
- Why purchase bills do not match portal data for input credit
- How to raise credit notes for returns without editing the invoice
- Item master cleanup: HSN codes, rates and units step by step
- Tax invoice, bill of supply and delivery challan: which when
- Typing e-way bills on the portal or raising them from the invoice
Let’s Build the Right Software for Your Business
Tell us about your current operational challenge, spreadsheet bottleneck, or software requirement. An experienced engineer will review your workflow and reply within one business day.
- No obligation consultation
- Senior engineer reviews your brief
- Your operational details stay 100% confidential
Start with your requirements
Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.
Share your requirementsRelated services.
API and System Integration
The plumbing underneath. This covers the connections between billing, authority systems, the accounting software and every other system that must agree with them when a bill is raised, cancelled or corrected.
ERP, CRM and Business Software Implementation
Invoicing is one module among many. Choose this when the ERP is being configured and rolled out across branches and the tax logic has to fit the rest of it.
Data Migration and Moving Off Spreadsheets
Dirty masters block clean invoices. Item masters without tax codes and party masters with invalid registrations are cleaned before they reach a live billing screen, where every gap would stop a save.
E-Commerce and Digital Commerce
Online orders have no counter. Online and dealer ordering needs the invoice, the tax and the return to be correct with nobody standing at a counter to fix them.