Near completion / private evaluation

An invoice is not just a PDF. It is a workflow that must remain traceable.

FiskalBill is a Studio Outsider web product for client and catalogue data, invoice preparation and tracking, PDF documents, controlled delivery and fiscal workflows, with an embedded Bill Copilot.

clients and catalogueinvoices and PDFstatus and auditBill Copilot

Request a private demo Review the product scope

FiskalBill product shellInvoice operations workspace

Operational problem

Billing becomes difficult when master data, documents, delivery and regulatory states live in separate places.

FiskalBill brings these steps into a reviewable workflow. The goal is not to hide responsibility behind automation, but to make every important state and confirmation easier to see.

DAT

Master data must stay consistent

Problem: Client, VAT, activity and catalogue data can drift between spreadsheets, documents and operator memory.
System: Structured client and product records provide a common starting point for invoice preparation.
Purpose: Operators can review the inputs before a document or integration flow is triggered.
Evidence: validation findings / incomplete records / correction rate

DOC

The PDF is only one output

Problem: Creating a visual invoice does not by itself cover validation, status, delivery or later retrieval.
System: Invoice records connect line items, totals, document generation and downstream actions.
Purpose: The document remains tied to its operational state instead of becoming an isolated file.
Evidence: generation status / retry state / delivery state

INT

Integrations need visible states

Problem: Fiscal, e-invoice, e-mail and AS4 steps can fail independently and require different follow-up actions.
System: The product models integration steps, responses and queues as explicit workflow states.
Purpose: A qualified operator can see what completed, what failed and what still needs review.
Evidence: queued / completed / failed / indeterminate

REV

Automation still needs accountability

Problem: AI suggestions and operational shortcuts become risky when the user cannot inspect or confirm the action.
System: Bill Copilot is designed as an assisted layer with preview, role checks and confirmation for consequential actions.
Purpose: The user remains responsible for the final business and regulatory decision.
Evidence: preview / confirmation / actor / audit event

Implemented product surface

The current build connects six working areas behind authenticated access.

The public scope below reflects the delivered application and repository. The final integration stage covers alignment with current Croatian Tax Administration specifications, production certificates, connection and conformity testing; that stage is not presented as complete yet.

CLICORE MODULE

Clients

Maintain client identity, contact, tax and business classification fields used by invoice workflows.

records / lookup

client profiles
OIB and VAT context
registry lookup integration points

CATCORE MODULE

Products and services

Maintain a reusable catalogue and classification fields for items added to invoices.

catalogue / NKD / KPD

reusable line items
classification context
validation and recommendation paths

INVCORE MODULE

Invoices and PDF

Prepare invoice drafts, line items and totals, then generate and retrieve the related PDF document.

draft / document

invoice workflow
PDF generation state
detail and history views

DELINTEGRATION FLOW

Delivery and regulatory flows

Connect e-mail, fiscal, UBL/e-invoice and AS4 steps through explicit states and integration boundaries.

e-mail / fiscal / AS4

queue and response states
UBL preparation
AS4 message monitoring

OPSCONTROL SURFACE

Users, audit and operations

Provide roles, settings, audit events and operational views for the people responsible for the system.

roles / trace / health

user administration
audit log
settings and operational panels

AICASSISTED WORKFLOW

Bill Copilot

Assist with searches, invoice preparation and structured operational actions while preserving preview and confirmation boundaries.

context / preview / confirm

guided search
action preview
role-aware execution path

Controlled workflow

Every invoice moves through states that can be reviewed separately.

This sequence is the product model. External availability, certificates and production credentials remain deployment-specific and must pass their own validation.

01
Master data
Review issuer, client, catalogue, VAT and classification inputs.
02
Draft and validation
Prepare line items, totals and warnings before a consequential action.
03
Document generation
Generate the PDF and retain its state with the invoice record.
04
Delivery and integration
Run only the configured e-mail, fiscal, e-invoice or AS4 path.
05
Status and evidence
Record responses, failures, retries, actors and audit context for review.

AS4 / Domibus integration layer

FiskalBill includes a zoned Docker gateway stack for controlled eDelivery work.

The repository contains the gateway topology, application callbacks, message records and monitoring assets. These are implemented integration and test surfaces; production interoperability still depends on the exact participant, P-Mode, certificates, endpoints and external acceptance tests.

ZONE

Four logical zones

The compose topology separates the reverse-proxy edge, application services, data stores and security/monitoring services.

DMZ / APP / DB / SEC network definitions

MSH

Domibus gateway runtime

A local Domibus build, database, reverse proxy, backend, queues and optional security services form the container stack.

compose services / health checks / persistent volumes

MSG

Outbound and inbound messages

Dispatch records, a callback contract with a token header, stored inbound payloads, retries and audit events connect gateway state back to the invoice.

AS4 routes / message model / callback contract

OBS

Operations and evidence

Prometheus metrics, a provisioned Grafana dashboard, an exporter contract and alert rules expose queue and delivery signals.

health / metrics / dashboard / alerts

Launch boundaries

The final integration stage includes current specifications, certificates and conformity testing.

“Near completion” describes the application and gateway build. FiskalBill remains in private pre-production evaluation until the current Tax Administration message profile, production certificates, endpoints, validation rules, roles and recovery procedures are verified end to end.

EVAL

Private evaluation

The hosted application remains behind authentication and is demonstrated in a guided, bounded session.

no public application link

REG

Final integration gate

The exact deployment must align with current Tax Administration message and security profiles, connect production certificates and pass the required conformity scenarios.

specification + certificate + conformity test

HIL

Human confirmation

AI suggestions and consequential actions require an authorised user and a reviewable confirmation path.

assistance / not autonomous authority

SEC

Data and access gate

Client identities, invoices, keys, audit records and operational settings must remain inside verified access controls.

synthetic or approved demo data only

Evidence before claims

The public page separates implemented modules from launch claims.

This lets a buyer understand the product without presenting an unfinished validation step as a certification or service-level guarantee.

Implemented scope

The application contains the listed modules and workflow surfaces.

Deployment-specific integrations

External fiscal, registry, mail, LLM and AS4 functions depend on configured services and credentials.

No automatic compliance

Software output does not replace accounting, tax, legal or regulatory review.

No public SLA claim

Availability, throughput and support levels are not claimed until they are measured and contracted.

Studio Outsider products

LedgerIntel and FiskalBill are presented separately because their maturity, risks and evaluation paths are different.

Open LedgerIntel POC

Private product evaluation

Want to review FiskalBill on a bounded invoicing scenario?

We can demonstrate the current workflow with synthetic or explicitly approved data and agree which launch gates matter for your environment.

Request a private demo