Skip to main content
GullySystem
Statutory and Compliance · Solutions

Raise the bill once, and let the invoice reference number and QR code come back onto it.

Where a tax authority requires electronic invoices, this prepares your invoice data in the format the authority expects and sends it through a service provider. The reference number and any signed QR code come back onto the printed bill. Nothing is keyed twice. Whether your business must do this at all, and whether what is reported is right, stays between you and your accountant. The configuration reflects your accountant’s instructions for each country, not a one-size-fits-all rule.

What it is

Two systems handle one bill. It is raised in the billing software, typed again into a portal or a bulk tool, and the reference number is copied back by hand. On a busy despatch day a few bills never make the trip.

Here the bill is raised once. The data goes to an e-invoice service provider and comes back with its reference number and QR code, printed on the copy that leaves your office. A bill that fails validation shows as failed, with the authority’s own reason, on a list somebody clears before evening. The software records and prepares data but gives no tax or legal advice, and it files nothing without your approval.

What it replaces

What your team uses today.

The module takes over these, one at a time, so nothing has to stop while it is set up.

  • Retyping invoices into a government portal
  • A sheet of reference numbers pasted from emails
  • A chat message to the accountant for each rejection
Where it goes wrong today

The problems this is meant to ease.

Invoices keyed again

The bill is raised in the billing screen and the same data is typed into a portal. Slips creep in, and a rejected invoice costs a day. Typos cost days.

Rejections are noticed late

An error comes back from the authority and sits in an inbox. The customer waits for an invoice that was not accepted. Delay hurts the buyer.

Reference numbers miss the bill

The acknowledgement number is on the portal but not on the copy given to the buyer. Matching them later is manual.

Who needs reporting is unclear

Counter sales and exempt supplies get mixed with invoices that must be reported. Staff do not know which is which.

Cancellations follow no rule

A wrong invoice is cancelled in billing and not in the portal. The accountant is left to reconcile by hand.

Inside the module

What e-invoicing does.

Invoice data in the required format

Buyer tax registration number, place of supply, product codes and line values are assembled the way the authority wants them, from the bill you already raised.

Sent through a provider you choose

We are not an e-invoice service provider. Your system connects to one, and the credentials and the agreement stay in your name.

Reference number and QR back on the bill

The acknowledgement number, the reference number and any signed QR code are stored against the invoice and printed on the copy that leaves your office.

Failures that stay visible

A rejected invoice sits on a list with the authority’s own error against it, until somebody corrects and resends it.

Which bills need one

Invoices outside the requirement are marked. A counter sale that never needed reporting is not reported.

Cancellation and credit notes

Some places allow cancellation only for a short window, after which a credit note is the route. The module follows whichever your accountant says applies.

Where it gets used

What this looks like in a working week.

Illustrative scenarios, written to show the shape of the work. They are not accounts of client systems.

A routine invoice

The billing clerk raises the bill as usual. The data goes to the provider, and the reference number and QR return to the printed copy.

A rejected invoice

A buyer’s registration number is mistyped. The invoice lands on the failure list with the authority’s message, and the clerk corrects and resends it.

A counter sale

A walk-in customer is billed at the counter. The invoice is marked as outside the requirement and is not sent.

A correction after sending

The accountant decides a credit note is the right route for a wrong bill. The note is raised and linked to the original invoice. The trail stays intact.

Who touches it

The people who open this every day.

Accounts assistant

Raises the bill and watches the failed list. That list should be empty by evening.

Despatch clerk

Prints the invoice with its QR code before the vehicle leaves the gate.

Your accountant

Gets reported invoices that agree with your books, and asks about the ones that did not go.

How it is set up

From first conversation to daily use.

  1. Confirm the requirement

    Your accountant states which invoices must be reported and under what rules. You get a written note of the settings we will use. Rules come from them, not us.

  2. Choose a provider

    You select a provider and sign with them in your own name. You pass the credentials for a test environment.

  3. Send test invoices

    Sample invoices go through the provider’s test side. You see the returned numbers and error messages on screen.

  4. Handle failures

    The clerk and the accountant try a rejection and a cancellation. You agree who corrects what.

  5. Switch to live

    Live credentials are entered by your team. Billing staff are walked through the daily routine and the failure list.

Measuring it

How you would know it is working.

Record where you stand before it goes live, so the change is measured against your own figures.

  • Invoices carrying a reference number
  • Invoices on the failure list, by reason
  • Rejected invoices corrected and resent
  • Cancellations and credit notes raised
  • Invoices marked as outside the requirement
How it fits

It is one part of a system, not an island.

A module earns its place by what it passes to the next one. These are the connections we set up most often.

  • Invoice management
  • An e-invoice service provider
  • Transport documents
  • Tax management
  • Accounting software
Common questions

Questions owners ask about e-invoicing.

Do we have to issue e-invoices?

That depends on the rules where you trade, and those rules change from time to time. Ask your accountant to confirm the position for your own registration before you build anything.

Does this file our tax returns?

No. It reports invoices and stores what came back. Returns are filed separately, by you or by your accountant, and the responsibility for what is filed does not move to the software.

What happens if the authority’s system is down when we despatch?

The bill is raised and queued, then reported when the system answers. Whether stock may travel while it stays silent is your accountant’s call. It is a rule and not a setting.

Is this needed if we already bill from our accounting software?

Probably not. Many accounting packages already report e-invoices through a provider. This is for businesses billing from a counter, a site or an operations system. Share how your bills are raised today and we will say where the e-invoice belongs.

What affects the cost of e-invoicing setup?

The number of invoice types, entities and countries drives it. The provider you pick and the accounting software linked add effort. Charges from the e-invoice provider sit outside our quotation, which lists our own work line by line.

How long before invoices can be sent?

That depends on your provider agreement and on how clean your customer tax data is. A release for standard invoices can come before special cases. You supply your accountant’s rules and credentials, and dates go into the proposal. Provider approval sets the pace.

Talk to us

Tell us how you handle e-invoicing today.

A spreadsheet, a register or another system: say which, and we will tell you plainly what is worth changing.

What happens after you share your requirements

  1. A senior engineer reads your answers. Nobody phones first.
  2. Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
  3. If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
  4. No call is booked and nothing is paid until you have read the note. Your details stay with us.

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 requirements