Features
Intelligent document processing and integration
We build Ublion for organizations that need to digitize huge varieties and volumes of semi- and unstructured documents. These organizations rely on a platform that becomes smarter over time to retrieve full data sets, generate required digital formats, and automate workflows.
FEATURE | FUNCTION |
---|---|
Trainable AI | Ublion comes with document AI models for documents but extra training can be needed to reach 100% processing automation. Training can be done through GUI or by connecting external systems to evaluate results. |
Document classification – type | Ublion determines the document type based on the document input. The document will be tagged in case the this information should be used later on in the automation process. |
Document classification – context | Ublion structures and attaches all document related meta data -like channel, document source, sender, receiver, document type, document size, and more- to the document to enable the processing. |
Full, validated, data sets | Ublion captures and structures data from documents. |
Document context determination gateway | Ublion uses a document context determination gateway to decide which processing pipeline must be used. For example, English written purchase invoices from a German business partner are processed in another ML pipeline than orders written in Dutch. |
Multi-language, multi-region | Ublion compares the found captured data with the Latin Dictionary and corrects wrong captured data with the most likely alternative. A user can validate these corrections in the GUI if necessarry. |
Cross data check – Invoices | Ublion validates amounts from the invoice header with the total amounts of the invoice item-lines. Bot the brut and net amounts are compared and validated. |
Mandatory fields – invoices | To increase data quality, Ublion validates invoices on the mandatory fields. Regardless the region they are from. |
Tax compliance – invoices | Keeping up with indirect tax (VAT, GST) regulations is challenging, especially when managing global suppliers. Ublion pre-validates country-specific tax requirements before issuing an invoice. Ublion is always up-to-date and currently supports the tax rules for European countries. |
PDF invoice converter – invoices | Ublion process entire invoice documents -header, lines, text. Generate from a PDF invoice:
– Electronic invoice file, such as UBL or ZUGFeRd, with embedded PDF (base 64); |
Full data sets | Ublion processes entire documents. It’s designed to constantly seek patterns in documents (like humans), learn from experience (like humans) and self-select the appropriate responses in situations based on that (like humans). |
Multi-entities | Managing invoices (and other documents) for businesses with multiple entities, administrations, and locations can be challenging, especially if each location is in a different country or has different processes in place. Ublion offers multi-entity businesses a unified, single document processing solution. |
Analytics and reporting | Get all the management tooling necessary to optimize your process, from global communication KPIs to employee level metrics. |
Compliance | We cover GDPR with event logging and make the Ublion cloud deployment work with your requirements, from the right standards to the right geography. |
Document file formats | Ublion processes any file format without complex setup. Examples are JSON, XML, Text Delimited, text positional, Native PDF, Image Scan, Photo. |
Format to format | Ublion uses an internal format to store the captured document data letting users free to generate literary any required format. Optionally, Ublion can validate these new generated formats on regulations, business rules, mandatory fields, and more. |
Data validation – any source | Ublion can read data from any external source to validate, correct, or enrich the captured document data. For example for credibility checks, CRM integration, or to improve the AI learning by cross-checking the data. |
Ublion offers a flexible infrastructure to process all the document types you need, and all the rules and integrations necessary for maximum automation.
FEATURE | FUNCTION |
---|---|
All-in-one document gateway | Ublion organizes and automatically process all your incoming document traffic. Regardless the channel, sender, receiver, type, format, language, tegion, and more. |
Any channel | Ublion offers pre-configured inbound and outbound channels for document transport. Channels and priorities can be managed in the GUI or API. |
Notifications and requests | To give users visibility and control, Ublion notifies users about each processing stage. Examples are processing confirmations, correction requests or status updates. |
Channel authentication | Supported Authentication protocols are : oAuth 1.0 , 2.0 , http Basic, and many more. |
Any source | To improve data quality, users can connect Ublion to any external source to enrich or auto-correct the captured document data. For example, you can make a connection with the chamber of commerce to validate, enrich, or correct supplier data. |
Universal integration | Ublion enables a non- intrusive communication in between third parties systems with format-to-format conversion. Users can connect to any system without necessity of changes. |
REST API | Ublion REST API enable users to be fully autonomous. They can build their own integrations and apps on top of Ublion. |
GraphQL API | Ublion GraphQL API enable user to consume, manage and automate content document content. GraphQL offer flexibility as users can define their own content (analytics) models. |
Low code iPaaS integration | Ublion partners with Blueway for companies who need low-code integrations. Blueway offers Process Governance to handle both IS (data) flows and human workflows, following the BPMN2 standard. Users can model master data repositories, determine the data quality criteria, automatically generate user interfaces and data acquisition/exposure web services, and have access to a pre-built connector library. |
Flow control | Cloud-based automation does not mean losing control. We give you all the tools to manage the process – and keep improving it together. |
Analytics and reporting | Get all the management tooling necessary to optimize your process, from global communication KPIs to employee level metrics. |
Launch and deliver document integration services
FEATURE | FUNCTION |
---|---|
Service catalog | Offer document processing and integration services to your users from curated catalogs. |
Self-service | Your users can manage their own services. |
Automation | Service provisioning can be partially or fully automated. |
Multi-tenant | Provide specific tenants for different user groups. |
Field | Description | Supported by Ublion API |
---|---|---|
BASIC INFORMATION | ||
Invoice document type | Possible values: credit_note, debit_note, tax_invoice (most typical), proforma, receipt, delivery_note or other | Yes, context recognition |
Invoice document language | Entire Latin alphabet. For example ces, deu, eng, fra, slk, dutch. | Yes |
Document ID | The ID of the document. | Yes |
Customer ID | The number by which the customer is registered in the system of the supplier. Often the CoC. | Yes |
Issue Date | Date of issue of the document. | Yes |
Due data | The due date of the invoice. | Yes |
Tax Point Date | The date of taxable event. | Yes |
Vendor Order ID | Internal order ID in the suppliers system. | Yes |
Delivery Note ID | Delivery note ID defined on the invoice. | Yes |
Place of Supply | Place of supply (the name of the city or state where the goods will be supplied). | Yes |
Payment Instructions | ||
Account Number | Bank account number. | Yes |
Bank Code | Sort code. Numerical code of the bank. | [BETA] |
IBAN | Bank account number in IBAN format. | Yes |
BIC/SWIFT | Bank BIC or SWIFT code. | Yes |
Terms | Payment terms as written on the document (eg. “45 days”, “upon receipt”). | Yes |
Constant Symbol | Statistical code on payment order. | [BETA] |
Payment reference | In some countries used by the supplier to match the payment received against the invoice. | Yes |
Specific Symbol | Payee id on the payment order, or similar. | No |
Payment Method | Payment method text description defined on a document (e.g. “Cheque”, “Pay order”, “Before delivery”) | [BETA] |
VAT & Amounts | ||
Total amount | Subtotal over all items, including tax. | Yes |
Amount Due | Final amount including tax to be paid after deducting all discounts and advances. | Yes |
Total Without Tax | Base amount for tax calculation. | Yes |
Total Tax | Total tax amount. | Yes |
Amount Rounding | Remainder after rounding amount_total. | [BETA] |
Amount Paid | Amount already paid. | Yes |
Currency | The currency which the invoice is to be paid in. Possible values: czk, dkk, eur, gbp, nok, sek, usd or other. | Yes |
VAT Rate | One of the tax rates in the tax breakdown. | Yes |
VAT Base | Sum of tax bases for items with the same tax rate. | Yes |
VAT Amount | Sum of taxes for items with the same tax rate. | Yes |
VAT Total | Text on document describing tax code of the tax rate (e.g. “GST”, “CGST”, “DPH”, “TVA”). If multiple tax rates belong to one tax code on the document, the tax code will be assigned only to the first tax rate. (in future such tax code will be distributed to all matching tax rates.) | Yes |
Vendor & Customer | ||
Vendor Name | Name of the supplier. | Yes |
Vendor Address | Address of the supplier. | Yes |
Vendor Company ID | Business/organization identification number of the supplier. | Yes |
Vendor VAT Number | VAT identification number of the supplier. | Yes |
Vendor Email | Email of the sender. | Yes |
Customer Name | Name of the customer. | Yes |
Customer address | Address of the customer. | Yes |
Customer company ID | Company identification number of the customer. | Yes |
Customer VAT number | Customer VAT Number. | Yes |
Customer Delivery Name | Name of the recipient to whom the goods will be delivered. | Yes |
Customer Delivery Address | Address of the reciepient where the goods will be delivered. | Yes |
Other | ||
Notes | Reviewer’s notes. | [BETA] |
Line Items | ||
Code | Can be the SKU, EAN, a custom code (string of letters/numbers) or even just the line number. | Yes |
Description | Line item description. Can be multi-line with details. | Yes |
Quantity | Quantity of the item. | Yes |
UOM | Unit of measure of the item (kg, container, piece, gallon, …). | Yes |
Unit Price Without VAT | Unit price without tax. | Yes |
VAT Rate | Tax rate for the line item. | Yes |
VAT | Tax amount for the line. | Yes |
Unit Price | Unit price with tax. Rule of thumb: amount = amount_base + tax. | Yes |
Total Amount | The total amount to be paid for all the items including the tax. | Yes |