User guide › Apps › rs.ge filing
This connector talks to the Georgian Revenue Service and nothing else. If you don't file in Georgia, you can skip this page entirely — nothing here applies to any other tax authority.
A connector, not a sidebar app
rs.ge is not something you open from the main menu. It's a connector plugged into the Reconciliation app, which is the hub for every external document your workspace exchanges with the outside world. That split matters for finding things:
| What you want | Where it lives |
|---|---|
| Credentials, entity links, health checks, auto-send toggles | The rs.ge settings page — reached from Reconciliation → Connectors → Open settings |
| What we sent, what came in, what failed | Reconciliation's Inbox, Outbox and Audit tabs |
| Filing one specific invoice | The Send / file dropdown on that record's drawer |
The rs.ge settings page is admin-only and deliberately absent from the settings rail — you reach it through Reconciliation. Saving credentials, running a test connection and authenticating are all admin actions. See Permissions & access.
Three services, one connector
rs.ge isn't a single system. BackOffice talks to three of its services, each with its own login style, which is why the settings page has more than one credential box.
| Service | What it handles | How it's authenticated |
|---|---|---|
| WayBillService | e-waybills — issuing, sending, closing, cancelling; the buyer-side inbox; PDF copies; tax-ID and VAT-payer lookups; tax invoices linked to a waybill. | A dedicated web-service user, sent on every call. There is no login step and no session. |
| NTOS | Standalone tax invoices — the ones with no waybill behind them. | Its own service user. If you don't enter one, the WayBillService credentials are reused. |
| EAPI | The employee registry, and the salary-declaration path. | A token you obtain by pressing Authenticate. Two-factor accounts get an SMS PIN prompt. |
You only need the credentials for the parts you actually use. Sending waybills needs WayBillService and nothing else.
Setting it up
Getting the credentials themselves is something you do at rs.ge, not in BackOffice — the generic pattern for adding a third-party connection is covered in Integrations. Once you have them:
- Open the connector settings Go to Reconciliation → Connectors, find rs.ge (Georgia Revenue Service) and click Open settings.
- Enter the service user Fill Username and Password under the credentials card and press Save. Saved secrets are never shown back to you — the fields go blank and the status line flips to configured.
- Pick the environment Production or Test. rs.ge does not run a separate sandbox host, so both settings reach the same service; the toggle exists so your audit trail can tell test activity apart from live filing. Test credentials are something rs.ge issues you.
- Test the connection Test connection pings rs.ge with your credentials and reports back immediately. Do this before you file anything — a rejected login here is much cheaper to fix than a rejected document later.
- Fill in the seller info Tax ID and Business name identify you as the issuing party on outgoing documents.
- Wire the entity links See below — this is the step people forget.
Extra services live under Advanced, collapsed by default: an NTOS override (username, password and user id, with its own Test connection) and an EAPI override. Leave them empty and the main credentials are used.
Entity links
The connector doesn't own its own invoices or employees. It reads yours. The Entity links panel on the settings page shows four roles and which of your entities is currently bound to each. A role showing MISSING means anything depending on it can't run.
| Role | What it feeds |
|---|---|
invoice-anchor | The invoices that get sent as waybills and tax invoices. |
buyer-anchor | The counterparties on those documents — this is where the buyer's tax ID is read from. |
employee-anchor | Employee records pushed to rs.ge's registry. |
payroll-anchor | Payroll records the salary declaration is built from. |
Link or create takes you to the entity-roles screen; Open in builder jumps to an already-linked entity. Installing the Invoices app is the usual way the invoice-anchor role gets filled. One entity can serve several apps at once — when that happens the panel names the other consumers underneath, so you don't mistake a shared entity for something rs.ge has taken over.
The connector installs fine with no roles wired. You'll see the missing badges on the settings page rather than an install failure — and sending will fail with a clear message until the role is assigned.
Employee registry sign-in
Anything that touches the employee registry or the salary-declaration path needs the EAPI token, which is separate from the other credentials.
- Press Authenticate In the employee registry card. The status line reads not authenticated until you do.
- Enter the PIN if you're asked Accounts with two-factor get an SMS code; a PIN box opens for it and the status shows PIN pending until you complete it. If you close the box, an Enter PIN button stays on the card.
- Check the status Once done the status reads as an active token and a Sign out button appears. Changing the EAPI username or password clears the token — you'll need to authenticate again.
Sending an invoice
Filing happens from the record, not from a batch screen. Open an invoice and use the Send / file dropdown in the drawer header. That dropdown is built from whatever the connectors can do with that record's role, so on an invoice you'll see the rs.ge entries; on a record with no role you'll see nothing.
| Action | Runs against | What it does |
|---|---|---|
| Send as rs.ge waybill | Invoices | Issues the invoice as a goods e-waybill and sends it in one step. |
| Send as rs.ge tax invoice | Invoices | Issues a tax invoice. If the invoice already has a waybill, it's filed against that waybill; otherwise it goes standalone through NTOS. |
| Sync employee to rs.ge | Employees | Pushes the employee record into rs.ge's registry. |
| File salary declaration | Payroll records | Builds the monthly declaration for that record's period. See the warning below before relying on it. |
Every entry is checked before you press it. An action whose credentials aren't set up is greyed out with the reason written underneath — "NTOS credentials not configured", "token not cached, authenticate in settings" — so you find out before the call, not after. Results appear inline on the drawer, and the record drawer grows a badge showing the document's number and current state.
Building and previewing the monthly declaration works. The final submit call is against a best-guess address on rs.ge's side, and if rs.ge rejects it the error message says so explicitly. Treat this as a draft/preview tool and confirm the filing through rs.ge's own channels — don't assume pressing the button filed anything.
Which document gets issued
Waybills and tax invoices aren't interchangeable, and the connector decides which applies by reading each line's item type:
| The invoice contains | What's issued |
|---|---|
| Goods lines only | A waybill. |
| Goods and services mixed | A waybill plus a tax invoice linked to it. |
| Service lines only | A standalone tax invoice — this is the NTOS path. |
So getting the item type right on your line items is what makes the routing right. Line items, VAT category and units all live on the invoice — Invoices covers the record side.
Sending automatically
The settings page ends with an auto-actions card listing the rs.ge actions that can fire by themselves when a record is saved — issuing the waybill the moment an invoice is created, or re-syncing an employee whenever their record changes. They're off until you turn them on, and they sit on this page rather than in Accounting so that a workspace filing somewhere other than Georgia never sees them. Salary declarations are deliberately excluded: monthly filings are meant to be a deliberate press.
An automatic action reaches a government service the moment the record saves. Switch it on once your entity links are wired, your line-item types are correct and a test send has come back clean — not on day one.
Supplier waybills coming in
Waybills your suppliers issue to you are pulled in automatically — the connector polls rs.ge every ten minutes for every workspace that has credentials saved. Nothing to schedule, and a workspace with no credentials is skipped in silence.
What arrives lands in Reconciliation → Inbox, one row per document, with the type, the document number, the counterparty, the amount and a status chip. Filter by connector when you have more than one integration running.
- Matched rows show the BackOffice record they belong to.
- Unmatched rows carry a Link to record action — paste the id of the record it belongs to and they're tied together.
Linking is an elevated action: it needs the Reconciliation app's execute permission, and the button is hidden without it. The rule is enforced on the server as well, so it can't be worked around.
Watching what happened
Reconciliation → Outbox is everything you've issued, with the same columns as the inbox plus the live status of each document — draft, pending, active, closed, cancelled or error. A failed document shows the error rs.ge returned right in the row, so you can usually see the cause without opening anything.
Reconciliation → Audit is the wire-level record: every call to every connector, with the operation name, the HTTP status, how long it took, any error and a timestamp. Requests and responses are stored, and passwords are stripped before anything is written. This is the trail you want when rs.ge queries a document months after the fact.
Reconciliation → Connectors shows each integration with a live health badge, the document types it receives and the actions it offers. A red badge here is the fastest way to confirm a filing problem is a credentials problem.
When something goes wrong
| What you see | What it means |
|---|---|
| The Send / file dropdown is empty on an invoice | That entity has no role tag, or no connector handles its role. Check the entity links panel on the rs.ge settings page. |
| An action is greyed out with a reason underneath | Exactly what it says — the credentials for that service aren't configured, or the employee-registry token isn't cached. Fix it in settings and reopen the record. |
| No invoice-anchor configured | Nothing is bound to the invoice role. Assign it from the entity links panel; installing Invoices is the usual fix. |
| Test connection is rejected | rs.ge didn't accept the login. The credentials must belong to a web-service user, which is a distinct thing from your ordinary rs.ge portal login. |
| A record has no valid period | The salary declaration reads a month off the payroll record and it wasn't in the expected YYYY-MM shape. |
| A document sits in error in the Outbox | rs.ge rejected it. The row carries their message; the Audit tab has the full exchange. |
Where this connects
- Invoices are the source of every outgoing document, and their line items decide which document type gets issued — Invoices & quotes.
- Accounting is unaffected by filing — the ledger and the tax filing are separate steps on the same records — Accounting.
- Credential setup for third-party services in general is covered in Integrations.
- Who can file is a permissions question — settings are admin-only and linking needs the execute capability — Permissions & access.