Connect Wegiel.io with documents, payments and workstations

Support fuel sales and the office with configured KSeF, GUS, bank-file import and supported fiscal connections. Weighing is a separately selected scope, checked for the actual device and operation. These connections do not close the known readiness limitation for calculated excise duty.

  • KSeF and GUS
  • Bank statements
  • Application and Chrome extension

Optional weighing connection at the fuel yard

The software can receive measurements from a supported weighing indicator over a network connection. The operator uses the retrieved weight in weighing, and its source remains recorded alongside the operation.

Device reading under operator control

The operator selects configured scales and retrieves a measurement. The software recognises the value and reading stability, recording the weight, time and person carrying out the action. Workstation rules determine whether a stable measurement is required.

Weight used in subsequent work

A measurement can be assigned to a weighbridge ticket. With two weighings, the software calculates gross, tare and net weight, and the saved ticket becomes the starting point for further documents. Manually entered values have a separately marked source, allowing the office to identify how the weight was obtained.

A connection selected for the specific scales

Before setup, we check the indicator model, how readings are transmitted and whether the connection is accessible from the service. We select the device profile, network settings and, if required, a converter for a network connection. A test reading verifies the correct weight and its recording in the selected process.

Before setup: Prepare the indicator model and documentation, connection method, and workstation and branch information. We confirm support for the specific setup when selecting the integration.

Documents and account settlements in one workflow

KSeF: invoice submission, receipt and statuses

Send invoices individually or in batches, and check their status, KSeF number and UPO alongside the document. Synchronisation retrieves received invoices, while business partner, product and cost mappings help prepare purchase documents, goods receipts and payables.

Before setup: Setup includes company access to KSeF, permissions, modules, and submission and synchronisation rules.

GUS: business partner data from the REGON register

Search for a company by NIP, REGON or KRS. Use registry data in the master record and review a proposed update before saving it. Reports also help handle entities with local units.

Before setup: The connection requires configured GUS access.

Bank statements: from file to settlement

Import MT940, CAMT.053 and CSV. The system matches transactions to documents using amounts and payment data, and handles partial payments, combined payments and overpayments. You can approve proposals and enable automatic settlement for unambiguous matches.

Before setup: Prepare a statement file from your bank. We select formats and matching rules to suit your documents and accounts.

Settlement and record-keeping principles

A document with a payment due date opens a settlement item for the business partner, and a payment, offset or correction changes that same item. Balances, history and tax records are therefore based on the same records.

An open item instead of a separate list of debts

A sales or purchase invoice or another liability creates an item with a due date and an outstanding amount. Settlements of the item cannot exceed that amount, and the item becomes partly or fully settled.

Partial, bulk and overpayments

One transaction can settle several documents or part of them. Any surplus is recorded as the business partner’s overpayment and can be allocated to another item.

Offsetting mutual items

The system proposes the oldest receivables and payables of the same business partner. The balance changes only after the offset is confirmed, and the confirmation can be withdrawn.

Bank statement and cash

The statement import recognises a file uploaded again and proposes matches by amount, document number, tax ID and account. A cash payment creates a KP or KW document, and the cash desk has a daily closing and a monthly report.

Due dates, reminders and collection

You send email or SMS reminders manually or according to a sequence: reminder, demand for payment, interest note. Statutory interest is calculated across rate periods, and a broken payment promise creates a task for the account manager.

Records and handover to accounting

A VAT register with JPK_V7 preparation, the KPiR book for companies that keep one, KSeF for invoices and a document package for the accounting office prepared on request.

The system organises entries and prepares the records. Responsibility for tax classification and for the correctness and filing of returns stays with the company and its accountants. Neither recording a payment nor an offset executes a transfer.

Stock layers and valuation methods

A receipt creates a layer with quantity, date and unit cost. An issue draws layers in the order defined by the warehouse valuation method and keeps track of which deliveries the cost comes from.

A method assigned to the warehouse

You can choose FIFO, oldest receipts first, LIFO, newest first, and a weighted average recalculated after each receipt. The company sets the default method and the methods allowed in forms.

Controlled change of method

A warehouse with movement history changes its method after the previous period is closed and before the first issue of the current one. A report compares stock value by different methods and by the periodic average.

Reservations without stock movement

Available quantity is physical stock minus active reservations. A reservation from a sales order is fulfilled by the invoice and the delivery note, and a manual reservation is released with a record of person and time.

Stock card and batch labels

The card shows receipts and issues with source documents, costs and balance. Batches can be marked with a QR label that is also recognised during stocktaking in the mobile app.

In the Wegiel.io package layers and reservations cover fuel records. Stock valuation does not automatically recalculate excise according to rate history.

Local applications and fiscal devices

Connect prepared retail receipts to a supported fiscal device. Confirm model, local application, workstation and configuration before the offer and order. Posnet hardware acceptance remains open.

Posnet Online

The Posnet Online integration is prepared according to the manufacturer’s API documentation. A separate local application connects the software with the device at the point of sale and links receipt handling with documents in the software. We activate it together with the first workstation equipped with a Posnet register.

Before setup: We select a compatible device model, the workstation application and the connection settings. The first activation includes a test on the customer’s device.

NoviAPI for Novitus devices

The proposed Novitus connection is intended to use a workstation bridge and the KasaIntegrator extension in Google Chrome with NoviAPI to submit receipts for fiscalisation, retrieve results and device status, and handle daily reports. The specific local application, device variant and configuration must be confirmed and checked before an offer or order.

Before setup: The supported device variant, local application, available workstation and network configuration must be confirmed and checked before an offer or order. Scheduled reports require an enabled rule and an available workstation.

Receipt-based sales and fiscal devices are a selected extension. The specific local application, device variant and configuration must be confirmed and checked before an offer or order; Posnet hardware support has not been accepted. KP/KW cash documents record cash receipts and payments in a separate workflow.

Google Chrome extensions

Connect a workstation to a fiscal device or prepare a data import from the public BDO register. We select tools to suit your modules, permissions and instance address. Any fiscal connection requires confirmation and checks of the specific local application, device variant and configuration before an offer or order; Posnet hardware support has not been accepted.

KasaIntegrator — Novitus with NoviAPI

The intended extension setup is to connect the cloud application with a Novitus device using NoviAPI on the company's network, to send prepared receipts for fiscalisation, show results and device status, and handle daily reports. The specific local application, device variant and configuration must be confirmed and checked before an offer or order.

Before setup: The specific setup requires Google Chrome, a compatible device, workstation network access, enabled fiscal support and pairing with your instance. The local application, device variant and configuration must be confirmed and checked before an offer or order. Scheduled reports require an enabled rule, a computer, a running browser and an available device.

  1. For a setup confirmed and checked before the offer or order, enter your instance address and the fiscal device address and port in the extension settings.
  2. For a setup confirmed and checked before the offer or order, save the connection, grant the browser access to the specified addresses and ask an authorised person to pair the workstation in the application.
  3. For a setup confirmed and checked before the offer or order, send the receipt prepared in the application for fiscalisation. Check the result alongside the document; manage device status and daily reports from the prepared workstation.

Data import from the public BDO register

The tool prepares business location data, decisions, permits and waste codes from the register for import. The scope covers your company or a business partner; the operator reviews the data before transferring it to the application.

Before setup: We enable data transfer after checking support for the instance address, user permissions and a trial import. The operator uses Google Chrome, signs in to the application in the same browser and completes the register's verification themselves.

  1. Once the connection is enabled, open the entity and relevant business location in the public BDO register and complete the required verification.
  2. Select registry data collection. Review the preview of locations, decisions, permits and waste codes.
  3. Select your company or a business partner and request the import. Check the application's response and the saved data before further use.

Registry data import is a separate tool from handling KPO and KPOK records and KEO, KEOK and KEON registers through the BDO API. We agree the BDO module scope and access to the registry tool separately.

Select extensions for your instance

A connection prepared for a specific task

  1. Data and outcome

    We define what should pass between systems or a device: company data, a document, weight, status or settlement.

  2. Access and responsibility

    We prepare the necessary accounts, permissions, workstation and rules. We identify the person who assesses the result and handles exceptions.

  3. Trial before launch

    We check the agreed workflow using sample data and confirm the connection scope in the implementation offer.

Connect the software to your business tools

Tell us which services and device models you use and the process you want to improve. We will select modules and an approach to setting up the integration.

+48 514 97 97 97

sprzedaz@wegiel.io

Screenshot preview

Screenshots have been omitted from the printout.

Your privacy

This website does not run optional analytics or advertising. Below we describe the data stored in your browser and the preferences you choose.

  • Browsing public pages does not create session or CSRF protection cookies.
  • We remember your chosen theme for the current session in this browser tab.

We use the information you share when contacting us to respond to your enquiry.

We will remember that you closed this window for the current browser session. This is a display preference. Closing the window does not mean consent to marketing or tracking.

Privacy settings

These settings apply to wegiel.io in this browser. They are not transferred to the customer portal or other domains.

Website operation and your preferences

  • Browsing public pages does not create session or CSRF protection cookies.
  • The light or dark theme you select with the button is remembered for the current session in this browser tab.
  • Closing the privacy notice is remembered for the current browser session. This is a display preference, not consent to tracking.

We use the information you share when contacting us to respond to your enquiry.

We currently use no optional analytics, advertising or embedded services that require your consent. You do not need to accept anything to use the website.