Products
RecUmi Docs
In developmentRecUmi Docs is a standalone product of the RecUmi ecosystem: quotes and contracts from templates using the data of the customer and your company; invoices and completion certificates are planned. A document is assembled without retyping and stays in the customer's history. The product is in development: there are no dates and no download button yet.
Templates of quotes and contracts, a catalogue of goods and work, and company details were used in the internal system of the company Time Rec; in the separate RecUmi Docs product these capabilities are being carried over and are not yet released.
The quote sits in one folder, the contract in another, and the customer's data is retyped each time — with mistakes in details and amounts. Docs assembles a document from what is already known and keeps it next to the customer. RecUmi Docs issues the documents an organisation uses to work with a customer: a commercial quote, a contract, then an invoice and a power of attorney. The data is entered once, the document is assembled from a template, the stamp and signature are already in it, and the customer gets a link and a file. It suits any organisation that issues quotes and signs contracts: construction and installation, trade, services, manufacturing, catering. The product makes no industry assumptions. What it removes: a document typed by hand in an editor, a stamp pasted as a picture, confusion over numbers, a file that cannot be recalled after sending, and the same contract drawn up differently by two managers.
Prepares a quote from a template in minutes and sees which documents the customer has already received.
Work with approved contract templates, not copies of old files.
The same details, stamp and signature of the company are inserted into all documents.
Dimensions and parameters from a measurement go into the quote without retyping.
Sees the amounts and the voiding of documents, who created and sent them and when.
Invoices for payment are a planned capability.
Employee permissions, templates and the organisation's details (your own details are planned).
A quote is assembled from a template, the customer's data and catalogue items.
Contracts for supply, installation or supply with installation — from approved templates.
A reference list of items with prices, from which quotes and specifications are assembled.
The details and the stamp and signature images will belong to your company and be inserted into its documents.
The finished document comes in formats for editing and for sending to the customer.
Quote and contract numbers are assigned automatically, without a log in a spreadsheet.
All of the customer's quotes and contracts — in their card, with dates and versions.
A document can be created from scratch, without a mandatory deal in CRM.
Invoices and certificates of completed work — in the same way, from the same data.
A document can be viewed before it is issued.
A supply contract, an installation contract and a supply-with-installation contract - from templates that come with the program.
The customer receives a link to the document; no account is needed.
For every document you can see who created it, who sent it and who voided it - and for what reason.
The recipient's details are saved inside the document.
The name and details are pulled from the state register of taxpayers by BIN.
If the print file is unusable or the document has no number, the document is not issued - you get a clear error with the reason.
Deleting a document is not final: it can be restored.
The stamp and signature images are embedded in the body of the document; integrity is checked.
Invoice: the recipient and their details, items, amount, payment deadline, purpose of payment, continuous number, PDF. Power of attorney: employee, authority, validity period, signatory.
A completion certificate (scope of work, amount, signatures of the parties) and a specification to the contract (a list with characteristics) are planned.
An electronic digital signature was discussed as an idea.
Four steps from data to document.
The whole path is a planned capability of the RecUmi Docs product.
Say or write which document you need, and RecUmi Docs will prepare a draft from the data of your 1C, show it to you and create the document in 1C only after your confirmation. Docs remains a standalone product: it works without 1C and without CRM.
Examples are illustrative. If details are missing, RecUmi will ask for them rather than make them up.
| Feature | What it does | Stage |
|---|---|---|
| Connecting your own 1C | An organisation connects its own 1C (first of all “1C:Accounting for Kazakhstan”); every organisation has its own 1C, its own data and access. | Planned |
| Organisation and legal entity | Before a document is created, your organisation and the legal entity on whose behalf it is issued are chosen. | Planned |
| Reference lists from 1C | Counterparties, employees, goods and services come from your 1C, within the user's permissions. | Planned |
| Invoice for payment | An invoice is created in your 1C from the command data and the reference lists. | Planned |
| Power of attorney | A power of attorney for an employee, for example to collect materials. | Planned |
| Document preview | A document can be viewed before it is issued: recipient, items, arithmetic and total are in place. Verified in the internal system of the company Time Rec. | Implemented, in testing |
| Confirmation before creating in 1C | A document is created in 1C only after your confirmation; until you confirm, nothing is written to 1C. | Planned |
| Printable form | The finished document is in PDF (and DOCX where applicable). | Planned |
| Voice command | A command by voice: RecUmi recognises what needs to be done and asks for the missing details. Right now speech recognition in RecUmi exists only for call recordings - there are no voice commands. | Planned |
| Text command | The same thing in plain text, without voice. | Planned |
| Link with RecUmi CRM | The customer and deal from CRM are filled into the document, and the document returns to the customer's history. | Implemented, in testing |
| Document link for the customer, with revocation | The customer is given a link with its own expiry; it can be revoked without affecting other links. Verified in the internal system of the company Time Rec. | Implemented, in testing |
| Sending from the app through communication channels | Sending the finished document to the customer straight from the app is planned. For now a person sends the link to the customer. | Planned |
| Historical requirements (02.10.2026) | The 1C task statement, restored from the Coordinator's decision: described below. This is a concept, not a working integration. | Idea, discussed earlier but not yet approved for development |
Status: a historical task statement, planned, needs confirmation. This is not a description of a working integration and not a confirmation that such a 1C interface exists. The source is the Coordinator's decision, restored not word for word.
The task: the system "1C:Accounting for Kazakhstan", edition 3.0; of the documents first of all an invoice for payment and a power of attorney; input from a phone by a voice or text command.
Sending to an external addressee requires separate confirmation: confirming the creation of a document is not permission to send it.
Principles of the task. 1C is the source of truth: for a document created in 1C, what is right is what is in 1C, not a copy in RecUmi. Voice is not permission: a person confirms consciously. The graphic stamp and signature are images, not an electronic digital signature.
In principle the system does not touch accounting until a person has looked and confirmed - which is why there are two confirmations in the chain. Details are taken only from a reference list or typed by a person, not "by ear": an error in one digit of a BIN costs more than a misheard word.
The 1C integration will be announced only after testing on a test 1C instance; there is no 1C connector yet. Configurations, hosting and permissions in 1C differ between organisations; we will name the supported options together with the release.
Important. These actions are implemented and verified in the internal system of the company Time Rec; in the separate RecUmi Docs product they have not yet been released to users. So this is a description of how the function works, not a user guide.
Void the document with a reason and issue a new one: the number is new, numbering is continuous.
The document will arrive as a DOCX with the reason stated. This is not a failure: the converter did not finish within the allotted time.
| Link | What it gives | Stage |
|---|---|---|
| CRM → Docs | The customer, site, items and details are carried into the document; the document remembers which deal it came from. | Implemented, in testing |
| Measure → Docs | A quote is prepared from the measurement result. The whole path is still being tested. | Implemented, in testing |
| Docs → customer | A link with a limited expiry and the possibility of revoking it. | Implemented, in testing |
| Calls → Docs | A conversation suggests that it is time to send a quote. | Implemented, in testing |
| Docs → 1C | A document is created in 1C, the printed form is taken from there. | Planned |
The illustrations on the site are made with fictitious data: a preview with the arithmetic "quantity × price = amount", a document with a stamp and signature, a list of issued links with an expiry and a revoke button, a choice of three kinds of contract, and a diagram of the chain with 1C labelled "planned". There are no real details, BINs, invoices, stamps or signatures on them.
Docs works on its own too: a document is created, previewed and issued as a file without a deal and without CRM - this has been verified in the internal system of the company Time Rec. An organisation that needs only documents does not need the other products. Together with other products, Docs receives the customer's and measurement data.
Planned Links between Docs and CRM, Measure and Service will appear together with the release of the products and the shared RecUmi Core foundation.
"Implemented, in testing" means the feature is implemented in a test or internal version and has not yet been made available to users as a finished public product. Where: in the technical version of RecUmi Docs built on the internal system of the company Time Rec (historically these functions worked in the internal system). This is not a live RecUmi service.
There are no dates on purpose: the owner has not confirmed them. The order is a concept, not a commitment.
A document is assembled from a template and structured data: customer, catalogue items, company details. The seal and signature in a document are images, not an electronic digital signature. Output formats are DOCX and PDF, as they become ready.
No. The product is in development; there is no download button. We do not name dates.
The stamp and signature in a document are images from your company's details, not an electronic digital signature. An electronic digital signature is an idea that needs confirmation; the legal force of a document is determined by your own signing procedure.
No. A document can be created from scratch. If you use CRM and Measure, the customer's and measurement data will be filled in automatically.
The idea is that a document can be checked in a preview and corrected before sending. This is a planned capability.
The details belong to the user's selected company; working with several legal entities is a planned capability.
History and versions of documents per customer are a planned capability.
Yes, working from your company's templates is the basis of the product. This is a planned capability.
We do not announce such a feature. A document is assembled from your templates and data; anything that appears beyond that we will announce only after it has been checked.
This is a planned capability: connecting an organisation's own 1C, and invoices and powers of attorney by command with confirmation. We will announce it only after testing on a test 1C instance.
No. RecUmi will prepare a draft and show it; a document is created only after your confirmation, and transactions and signing stay with you.
Both formats are issued. The first document after the system starts may come as Word if the converter did not finish in time - the system will say so itself. Both formats have been verified in the internal system of the company Time Rec.
Not yet - it is planned. For now the program holds the data of one organisation.
The link can be revoked. Each link has its own expiry, and revoking one does not break the others.
Not yet - it is planned, and it is the nearest item in the plan.
Not yet. Speech recognition exists in the system, but only in Russian and only for call recordings; there are no voice commands for documents.
Numbering is continuous; a document without a number is not issued - the system will refuse and say why.
Not yet - it is planned. For now a link is issued, and a person sends it.
Tell us which documents you prepare most often — it will help us make the templates more useful.