INP File Interface

The INP file interface provides a file-based integration method for fiscal operations. The driver monitors a dedicated directory for each INP-enabled fiscal device; when a command file is placed in that directory, the driver processes it and generates the corresponding result files.

Setup and Configuration

To enable INP file processing for a fiscal device:

1. In the FisCool UI, open the fiscal device configuration
2. Enable the "INP Compatibility" option
3. Set an "INP Directory" (e.g. C:\FisCool\INP)
4. The driver begins monitoring that folder for new files

The driver automatically creates the result subdirectories BonOK, BonERR and BonANSWER inside the INP directory.

File Detection and Processing

• Files with the extensions .inp, .txt or .bon are always processed as INP commands.
• Files with other extensions are processed only if their content is recognisable as INP commands; otherwise they are ignored.
• Files larger than 1 MB are ignored.
• Encoding: UTF-8 is recommended. Files that are not valid UTF-8 are decoded as Windows-1252 (legacy compatibility). Non-breaking spaces are normalised to regular spaces.
• Empty lines and comment lines starting with # or // are ignored.

Processing Lifecycle

Output Directory Structure

• <INP Directory>\BonOK\ - successfully processed input files (moved intact)
• <INP Directory>\BonERR\ - input files that failed (with error details appended)
• <INP Directory>\BonANSWER\ - answer files (same name as the input file) with the operation results

Input File Format

INP files are plain text files with one command per line. Two command syntaxes are supported:

The syntax is detected automatically for every file, based on the commands it contains - do not mix the two syntaxes in the same file. The format of the answer and error files follows the syntax of the input file (see Answer File Format below). Commands are case-insensitive; UPPERCASE is recommended.

Example INP File - Legacy / FPrint

S,1,______,_,__;Coffee;2.50;1.000;1;1;1;0;0;buc
T,1,______,_,__;0;2.50;;;;

Example INP File - Simple / Modern

S^Coffee^250^1000^buc^1^1
P^1^250

Legacy / FPrint Format - Command Reference

Each command starts with a command letter followed by the standard header ,1,______,_,__; the parameters after the first ; vary by command type.

S,1,______,_,__;Coffee Espresso;2.50;1.000;1;1;1;0;0;buc
S,1,______,_,__;Bread 500g;1.20;1.000;1;1;2;0;0;buc
S,1,______,_,__;Fuel Premium;1.45;25.500;3;1;1;0;0;l

T,1,______,_,__;0;20.00;;;;   <!-- 20.00 cash -->
T,1,______,_,__;1;15.50;;;;   <!-- 15.50 card -->
T,1,______,_,__;4;;;;;        <!-- type 4 with EMPTY amount = subtotal -->

C,1,______,_,__;1;5.00;;;;    <!-- 5% discount on the previous line -->
C,1,______,_,__;3;2.50;;;;    <!-- 2.50 value discount -->
C,1,______,_,__;0;10.00;;;;   <!-- 10% surcharge -->

P,1,______,_,__;Thank you;for your visit;Welcome back;;;

K,1,______,_,__;RO22352741;

I,1,______,_,__;0;100.00;;;;   <!-- deposit 100.00 -->
I,1,______,_,__;1;50.00;;;;    <!-- withdraw 50.00 -->

Z,1,______,_,__;0;      <!-- X report -->
Z,1,______,_,__;1;      <!-- Z report -->
Z,1,______,_,__;3;      <!-- departments report -->
A,1,______,_,__;;;X;;;  <!-- X report (A form) -->

DS;        <!-- open with the driver/device default pulse -->
DS;200     <!-- open with a 200 ms pulse -->

54,Plain text^^^^^^
54,Bold text^1^^^^^
54,Bold, double height, centered^1^^1^^1^

Simple / Modern Format - Command Reference

The simple/modern syntax uses ^ as the field separator, without the FPrint header. All monetary values are transmitted in bani (integer, 2 implied decimals: 250 = 2.50 lei), quantities with 3 implied decimals (1000 = 1.000) and percentages with 2 implied decimals (500 = 5%). The ^ character must not appear inside values.

S^Coffee Espresso^250^1000^buc^1^1
S^Bread 500g^120^1000^buc^2^1
S^Apples Golden^850^120^kg^1^1      <!-- 0.120 kg at 8.50 lei/kg -->

S^Coffee Espresso^250^1000^buc^1^1
VS^Coffee Espresso^250^1000^buc^1^1   <!-- cancels the line above -->
S^Cappuccino^400^1000^buc^1^1
P^1^400

P^1^2000        <!-- 20.00 cash -->
P^2^1550        <!-- 15.50 card -->
P^1^1000
P^2^1300        <!-- mixed payment: 10.00 cash + 13.00 card -->

S^Coffee^1000^1000^buc^1^1
DP^1000                          <!-- 10% discount on the coffee -->
P^1^900

TL^Thank you
TL^for your visit

CF^RO22352741
S^Coffee^250^1000^buc^1^1
P^1^250

I^10000     <!-- deposit 100.00 -->
O^5000      <!-- withdraw 50.00 -->

TL^-------------------------
TL^POS TEST SLIP
TL^-------------------------
VB^

Complete INP File Examples

S,1,______,_,__;Coffee;2.50;1.000;1;1;1;0;0;buc
S,1,______,_,__;Croissant;1.80;1.000;1;1;2;0;0;buc
T,1,______,_,__;0;4.30;;;;

S,1,______,_,__;Laptop Computer;899.99;1.000;2;1;1;0;0;buc
S,1,______,_,__;Mouse Wireless;25.50;1.000;2;1;1;0;0;buc
C,1,______,_,__;1;5.00;;;;
T,1,______,_,__;1;924.21;;;;

S,1,______,_,__;Fuel Premium;1.45;40.000;3;1;1;0;0;l
T,1,______,_,__;0;50.00;;;;
T,1,______,_,__;1;8.00;;;;

K,1,______,_,__;RO22352741;
S,1,______,_,__;Professional Service;150.00;1.000;1;1;1;0;0;buc
T,1,______,_,__;1;150.00;;;;

S,1,______,_,__;Product A;10.00;1.000;1;1;1;0;0;buc
P,1,______,_,__;Thank you for;your purchase;Welcome back;;;
T,1,______,_,__;0;10.00;;;;

P,1,______,_,__;--- ORDER #42 ---;;;
P,1,______,_,__;2x Coffee;1x Croissant;;
P,1,______,_,__;--- END ---;;;

I,1,______,_,__;0;100.00;;;;

Z,1,______,_,__;0;
Z,1,______,_,__;1;
Z,1,______,_,__;3;

The same operations in the simple/modern syntax (one operation per file):

S^Coffee^250^1000^buc^1^1
S^Croissant^180^1000^buc^2^1
P^1^430

CF^RO22352741
S^Notebook A4^380^5000^buc^1^1
DP^500
TL^Eco tax included in price
P^1^1000
P^2^805

I^10000     <!-- deposit 100.00 (own file) -->
O^5000      <!-- withdraw 50.00 (own file) -->

X^
Z^
D^

Answer File Format (BonANSWER)

Answer files are created in BonANSWER/ with the same name as the input file. The answer format follows the syntax of the input file.

Legacy / FPrint Answers (INI format)

Receipt Response

[Answer]
SlipNumber=123
nZrep=45
nFNum=1050

Daisy devices only: for compatibility with POS software configured for legacy Daisy drivers, the following extra fields are appended:

CommandName=close_fiscal_receipt
Allreceipt=000123      ; all receipts (fiscal + non-fiscal) since the last Z, zero-padded to 6 digits
FiscReceipt=000098     ; fiscal receipts since the last Z, zero-padded to 6 digits
DeviceSerial=8000596182

Report Response (X/Z)

[Answer]
nRep=42
TaxA=125.50
TaxB=67.80
TaxC=0.00
TaxD=0.00
TaxE=0.00

TaxA–TaxE are the daily sale totals per VAT group, in currency units with 2 decimals.

The departments report (type 3) prints only on paper and returns no totals - its answer file uses the generic Status=0 shape below.

Cash Operation Response

[Answer]
TotalCash=1250.75

TotalCash is the drawer total after the operation, in currency units.

Other Operations (e.g. open drawer)

[Answer]
Status=0

Simple / Modern Answers

Files written in the simple/modern syntax receive a compact key=value answer instead:

Receipt Response

BONOK=1
NRBON=123

NRBON is the fiscal receipt number.

Other Operations

Error File Format (BonERR)

The error format also follows the syntax of the input file.

Legacy / FPrint Errors

Error files contain the original INP content followed by the error details as comment lines:

S,1,______,_,__;Produs Test;10.50;1.500;120;1;1;0;0;kg
#Linia 1 | S,1,______,_,__;Produs Test;10.50;1.500;120;1;1;0;0;kg
#ErrorCode (-112207) : Valoare incorecta a parametrului departament.

• Parse errors use negative codes in the -112200…-112231 range and reference the offending line.
• Execution errors (device/communication errors after successful parsing) use Linia 0 | Execution Error and carry the driver's standard error codes (see Error Codes - e.g. 500 no paper, 1004 device not connected):

S,1,______,_,__;Produs Test;10.50;1.500;1;1;1;0;0;buc
#Linia 0 | Execution Error
#ErrorCode (1004) : Problemă la conexiune: Dispozitivul refuză conexiunea

Simple / Modern Errors

For files in the simple/modern syntax, the BonERR file contains a compact key=value error instead:

BONOK=0
ERRCODE=-112203
ERRINFO=Preț invalid.

ERRCODE uses the same codes as the legacy format: negative codes for parse errors, the driver's standard positive codes for execution errors.

Best Practices

• File naming: use unique, sequential file names to avoid conflicts.
• Result monitoring: watch BonANSWER and BonERR for the outcome of each file; the outcome file always has the same name as the input file.
• Encoding: prefer UTF-8; Windows-1252 is accepted for legacy compatibility.
• Separator: never use the field separator inside values - ; in legacy/FPrint files, ^ in simple/modern files.
• Single writer per file: write the file completely (or write to a temporary name and rename) before the driver picks it up.
• One monitor per folder: only FisCool should process the INP directory to prevent race conditions.
• Disk space: BonOK and BonANSWER accumulate over time - archive or clean them periodically.

Integration Notes

The INP file interface is ideal for:

• Legacy system integration: systems that cannot use the HTTP/WebSocket APIs
• Batch processing: queued receipt printing
• Reliability: file-based operations provide natural persistence and a built-in audit trail
• Debugging: input, answer and error files fully document every transaction