AI assistant for businesses

What is Kili?

Kili was an AI-powered document processing and administrative assistant designed for businesses, used to extract structured data from PDFs, images, documents, and spreadsheet files. Users defined fields through the Board interface, and then uploaded files in bulk, forwarded them via email, or imported them by using APIs.

The official homepage now clearly states that the team is no longer developing Kili, and has focused all its efforts on the voice response and scheduling service AIDE. Therefore, this entry is intended to provide information about its past capabilities and older packages; Kili should no longer be considered a tool that is still under maintenance and available for purchase.

Current operating status

A one-sentence summary

Kili is a code-free AI document extraction tool whose development has been discontinued; it used to support Board field configuration, batch or email import, data validation, automation, and integration with accounting systems.

Core working method

Kili uses Boards to organize documents of the same type. Each Board contains the fields that need to be extracted; once the file processing is complete, each document corresponds to a structured record.

• Create separate Boards for different document types.
• Define field names, descriptions, and data types.
• Upload a sample document to let the system recommend fields.
• Batch upload, import files via email, or API
• Automatically extract and format structured data.
• Values with missing, duplicate, or irregular markers
• Manually check and edit the final results.

Board field configuration

The Board functions as an extraction table specific to a particular document. The field names and descriptions help the AI locate the relevant information, while the data types, mandatory requirements, and uniqueness rules ensure consistent output.

• Express the target data using clear field names.
• Specify the context and extraction rules in the description.
• Select display types such as text, numbers, dates, etc.
• Set the fields that must be present as Required.
• Set invoice numbers, order numbers, etc. to be unique.
• First, use a small sample to verify the field design.
• Retain representative test documents for different layouts.

File import method

The historical help documentation lists three methods of import: batch upload, dedicated email address, and API. Once the processing is complete, Board is updated automatically, and notification settings for such processing can also be configured.

• Upload local files in bulk on the Board interface
• Forward the attachment to the dedicated email address.
• Submit files programmatically via API
• Wait for the platform to complete document processing.
• View new records and extraction status on the Board.
• Receive notifications of completion via email
• Manual inspection is carried out for failed or abnormal files.

Supported document types

Kili is designed for extracting data from unstructured files; the documentation specifically mentions PDFs, images, plain-text documents, and Excel files. The old tool page also covers a variety of business document templates.

• Supplier bills and customer invoices
• Purchase orders and customer orders
• Bills of lading, packing lists, and logistics documents
• Insurance policies and claim documentation
• Contracts and lease agreements
• Resume and candidate materials
• Custom industry documents

Invoice data extraction

Invoices are a crucial aspect of Kili; the system can extract the invoice number, date, expiration date, supplier, amount, and various line items. The older payment plans also offered transaction categorization and integration with QuickBooks.

• Extract data from PDF attachments and email bodies
• Identify the invoice title, number, and key dates.
• Extract the total amount, tax amount, currency, and line items.
• Check the required fields such as the VAT number.
• Identify duplicate invoice numbers
• Assign transactions to accounting categories
• Transfer the final data to the accounting or ERP system.

Matching of three invoices

Official articles recommend matching invoices with internal documents such as purchase orders and receipt records on a three-document basis, and referring those records with high amounts or those that cannot be matched to manual processing. The old version of Kili does not provide evidence that all packages come equipped with a complete matching module.

• Verify the supplier and basic invoice information
• Check the quantity and price against the purchase order.
• Verify the actual delivery by comparing it with the receipt records.
• Apply approval rules based on amount and supplier.
• Transfer records that are missing, out of specification, or high-risk to manual processing.
• Record the final approval, rejection, and reasons for any exceptions.

Data verification

Kili will generate output in accordance with the rules related to field types, mandatory fields, and uniqueness requirements, and it will mark any missing or duplicate values. The business logic and cross-system verification still need to be designed by the enterprise itself.

• Format dates, numbers, and text according to data type specifications.
• Mark required fields that are not found in the document
• It was found that the invoice number and order number are identical.
• Check whether the extracted value meets the field description.
• Manually verify records with low confidence and anomalies.
• Use the corrected data as a basis for subsequent quality analysis.

Manual editing

Users can open the editing interface from the record menu; the original file is displayed on the left side, while the fields to be modified are shown on the right side. This layout is suitable for checking for missing, inaccurate data, or changes that have occurred later on.

• View the original document and structured fields simultaneously
• Modify incorrect or incomplete extraction results.
• Data missing from the supplementary documents but known within the business
• Save the revised final record
• Complete quality review before exporting or integrating.
• Maintain the manual approval process for key fields.

New fields and historical data filling

When business requirements change, users can add new fields to Board and have the system fill them in using the existing documents. It is recommended to first test these descriptions on 3 records before applying them to all documents.

• Add new data fields
• Enter a name and a detailed description for the field.
• Choose to test only 3 historical records.
• Check the extraction quality in different layout formats.
• Process all records after correcting the description.
• It is also possible to create the fields first without filling them in immediately.

Automated actions

The older version of automation is in the Beta stage; it can be triggered when new records are created or existing records are updated. The actions available can use fields from the Board as input.

• Send an email notification after adding a new record
• Conducting research on individuals, companies, or entities
• Push the extraction results to an external destination
• Use slashes to reference existing fields.
• Re-trigger the action when the associated field is updated.
• Run 3 records first, then execute in batches.
• Monitor failures and repeated executions.

Integration of accounting and ERP

The old Solo and Starter plans list QuickBooks integration as an available option, while the Team plan supports integration with any accounting or ERP system. The scope of custom connections, two-way synchronization, and error handling need to be specified in the existing contract.

• Map invoice fields to accounting software
• Assign transactions to the appropriate categories.
• Transfer supplier, amount, and line item data
• Reduce manual data entry and format conversion
• Intercept duplicates, missing items, and synchronization failures.
• Retain approval and audit records before final recording.

Typical use cases

• The accounts payable team handles supplier invoices.
• Logistics companies obtain bills of lading and packing lists
• Enter customer orders in sales operations.
• The purchasing team organizes the purchase orders.
• The insurance team handles policy and claim documents.
• The legal team extracts the contract and lease terms.
• The recruitment team organizes the fields in resumes.
• Small and medium-sized enterprises convert email attachments into structured data.

Which users are it suitable for

• Existing customers who need to understand the old Kili data and workflows
• Teams that are exporting Kili records or assessing the scope of migration
• Researchers who work with no-code tools for extracting product design documentation
• Administrator responsible for verifying historical purchase contracts and package benefits
• Not suitable for new customers who are looking for new tools that require long-term maintenance.

Old version price of Kili

The prices listed below come from the historical pricing page that is still online; however, the developers have stopped working on Kili, so these prices cannot be considered as current purchase rates. New users should not submit any production data or make long-term purchasing decisions just because the page is still accessible.

Comparison of features in old plans

Message and page limits

The historical pricing page retains messages and page quotas, but the FAQ answers are not fully displayed on this current static page. Existing customers should rely on their old contracts, bills, and the actual measurements from the backend; they should not rely on marketing materials to determine the rules regarding excess usage.

• Confirm the specific AI action corresponding to a message.
• Find out how to calculate the page quota for multi-page PDFs
• Check whether failure verification, retries, and historical data filling are counted.
• After checking for excess usage, should it be disabled, have its speed limited, or be subject to additional fees?
• Save records of past bills and evidence of package benefits
• Calculate the average and peak monthly usage before migration.

Basic usage tutorial

1. Log in to your existing Kili account and check which Boards are still accessible.
2. Confirm the fields, types, and validation rules for each document.
3. Use a small number of non-sensitive files to verify whether the current processing is still functional.
4. Check the status of batch, email, and API imports.
5. Manually verify the extraction results and abnormal markers.
6. Export the data, field configurations, and original key files immediately.
7. Record automation, integration, and permission dependencies.
8. Establish a migration schedule rather than increasing new usage.

Invoice processing tutorial

1. Create an invoice board and define the fields for number, date, and amount.
2. Set required, unique, and correct data types.
3. Import samples from different suppliers and in various formats.
4. Verify the output for line items, tax amounts, and currency.
5. Add verification of purchase order data and delivery receipt data.
6. Have finance review unusual and high-value invoices.
7. Test the accounting system mapping and duplicate write protection.
8. Export historical records and approval evidence before migration.

Migration tutorial

1. List all Boards, fields, users, files, and automations.
2. Export structured records and the original documents.
3. Save the field descriptions, required status, uniqueness settings, and data type settings.
4. Record email entry points, API, and accounting integration dependencies.
5. Choose an alternative platform that supports ongoing maintenance and data export.
6. Use the same set of samples to compare extraction and verification quality.
7. Run it in parallel for a period of time and verify the final accounting results.
8. Confirm that the data has been deleted before terminating access to the old system.

Suggestions for alternative tool choices

1. Determine the type of core document based on invoices, logistics information, or contracts.
2. The candidate tools are required to handle real, complex layouts.
3. Compare fields, tables, handwriting, and multilingual capabilities.
4. Check manual review, confidence level, and audit logs.
5. Verify email, API, accounting, and ERP integration.
6. Verify the data region, training purpose, and deletion mechanism.
7. Calculate the total cost of pages, documents, fields, and manual review.
8. Give priority to platforms that allow the export of configurations and data.

Security and data migration

Once the development of a product is halted, uncertainties regarding security updates, service continuity, support response times, and data retention increase. Existing customers should prioritize confirming the arrangements for their accounts, data storage, backups, and data deletion.

• Stop uploading new sensitive or critical production materials.
• Export the original file, results, configurations, and audit records
• Rotation was once used for Kili’s API keys and integration credentials.
• Revoke email forwarding and system permissions that are no longer needed.
• Confirm the data processor and storage location
• Confirm in writing with the authorities the dates for data retention and deletion.
• Complete permission and security assessments on the new platform
• Retain migration checksums and evidence of final deletion

Effect evaluation

Historical advantages of the product

• A document extraction Board can be created without any code.
• The field descriptions, types, as well as the rules regarding necessity and uniqueness are clear.
• Supports multiple import methods, including batch, email, and API.
• New fields can be added to existing documents.
• The original document and the edited fields are displayed side by side for easy manual verification.
• It used to offer integration with QuickBooks and enterprise ERP systems.
• Automated actions can reference extracted fields.
• The prices of the older version are more intuitive for small teams.

Usage restrictions and precautions

• The development has been halted by the authorities; it represents a significant use risk.
• The fact that the old pricing page is still online does not mean that the packages can still be purchased.
• There are no guarantees regarding the availability of services and security updates in the future.
• The help documents and feature pages may be taken offline at any time.
• Historical automation is labeled as Beta; its stability cannot be assumed.
• The old FAQ does not fully disclose the rules regarding excess amounts and measurement.
• Errors in extraction still require manual review and business verification.
• Errors in accounting entries can have financial and compliance implications.
• New users should choose an alternative platform that is still under maintenance.
• Existing customers should export and migrate their critical data as soon as possible.

GitHub and open source

The official Kili website and its documentation do not provide any links to an official GitHub organization that can be verified. There are multiple accounts with the same name on public platforms, but the information related to those companies, their domain names, or the scope of their projects does not correspond reliably to the Kili.so product.

The Kili core document processing platform is not an open-source project; its complete source code and license are not made available to the public. Once development of this product stops, it cannot be maintained further using the official open-source code.

Basic information

Recommendation score

1.5 / 5. Kili used to offer a clear no-code field design, document import, and financial integration capabilities, but development on it has been halted by the developers; it is not suitable for new users to purchase. Existing customers should focus on data export, revocation of permissions, and verification of data migration.

Frequently Asked Questions

Can Kili still be used?

Some of the old pages are still accessible, but the official website clearly states that the team has stopped developing them; therefore, it should not be assumed that the production services will remain available in the long term.

Why did Kili stop development?

According to the official statement, the team identified opportunities for corporate voice interactions while developing voice-related functions, and decided to focus all their efforts on the new product AIDE.

What did Kili do before?

It extracts structured data from PDF, image, document, and spreadsheet files, and supports verification, editing, and automation.

How much did Kili cost originally?

The old version of Free costs $0; Solo costs $29 per month, Starter costs $49 per month, and for Team plans, it is necessary to contact sales.

Are the old prices still valid?

It cannot be confirmed. Development of this product has been halted, and the old pricing is only for historical reference; it should not be considered as the current price.

Does Kili support invoices?

Historic products supported the extraction of invoice fields and line items, and also offered integration with QuickBooks, transaction categorization, and ERP systems.

Does Kili offer an API?

The historical documentation indicates that it is possible to submit files via API and receive the results of processing; however, the current availability of this feature must be verified using an existing account.

What are Kili’s new products?

The team is now turning to AIDE, an AI voice assistant that helps businesses handle calls and schedule appointments.

Is Kili open source?

It is not open source, and there is no verifiable official GitHub code available for users to maintain on their own.