Budget: 5000 UAH Deadline: 3 days
Good day. I have extensive experience in developing Telegram bots in the programming language Python. Write to me privately for clarification of details. I will be happy to collaborate!
Telegram bot for invoice approval in the group of companies.
1. Selection of companies - K1, K2, K3
2. Users: Group 1 - invoice initiator (submits the invoice to the bot, enters the recipient of funds, amount, subject of procurement + uploads the invoice file), Group 2 - invoice approver (accepts or rejects), Group 3 - executor (receives the invoice upon approval), Group 4 - auditor (checks/downloads data on approved invoices for a certain period)
3. The bot must store all approvals in tabular form (date of submission, date of approval, initiator, company, recipient, amount, subject of procurement, link to the invoice file).
Budget: 5000 UAH Deadline: 3 days
Good day. I have extensive experience in developing Telegram bots in the programming language Python. Write to me privately for clarification of details. I will be happy to collaborate!
Budget: 5000 UAH Deadline: 2 days
Hello. I can develop this Telegram bot. Write to me - we will discuss.
I will support your project and fix issues even after the completion is confirmed.Budget: 15000 UAH Deadline: 7 days
Hello. I have extensive experience in developing Telegram bots. I am ready for collaboration.
Budget: 4999 UAH Deadline: 2 days
Good day!
I professionally develop Telegram bots and internal corporate systems in Python. I am ready to implement a bot for invoice approval according to your specifications: with user roles, saving approval history in a table/database, file uploads, and deployment on a server.
I have experience creating bots for internal document flow and financial control ✔️ (working with multiple access roles, approvals, and saving a large number of files).
Please let me know if you plan to store data in a separate database (PostgreSQL/MySQL) or if integration with Google Sheets is sufficient?
I suggest we communicate — I will provide a free consultation on optimal architecture and functionality, after which I will prepare a clear implementation plan and an estimate for timelines and budget.
Write to me in private messages — we will discuss the details.
I will do it for -3900.
Budget: 10001 UAH Deadline: 10 days
Good day 👋
I can implement a Telegram bot for invoice approval in a group of companies with full role separation and history of approvals.
🔹 Functionality
1️⃣ Company Selection
When creating an invoice, the initiator selects K1 / K2 / K3.
2️⃣ User Roles
Initiator
creates the invoice
enters the recipient of funds
amount
item of purchase
uploads the invoice file
Approver
receives notification
accepts or rejects the invoice
approval date is recorded
Executor
receives the confirmed invoice
sees all details and the file
Auditor
views all approved invoices
filters by date
exports to Excel / Google Sheets
🔹 Data Storage
The following are recorded:
date of entry
approval date
initiator
company
recipient
amount
item of purchase
status
link to the file
🔹 Implementation Technologies
Python + telebot — development of the Telegram bot
PostgreSQL — storage of invoices and roles
SQLAlchemy — ORM for working with the database
Google Sheets API (optional) — for synchronization or reports
DigitalOcean / VPS — deployment
Redis (if needed) — for managing states and approval queues
The architecture will allow:
adding multi-level approval
keeping an action log
scaling the system for a larger number of companies
💰 Estimated budget: 10,000 UAH
⏱ Implementation period: 10–14 days
I have experience in creating corporate Telegram bots with financial processes and access roles. I am ready to discuss the details of the approval (1 level or multiple) and propose an optimal structure for your working model.
Budget: 20000 UAH Deadline: 1 day
Good day,
I am ready to take on your project. I have experience in developing bots for automating business processes. I will be able to create a Telegram bot for invoice approvals in a group of companies, taking into account all the specified functionalities. The bot will collect and store data in tabular form, allowing for convenient tracking of all approvals.
My rate is $16 per hour. To start working, it is necessary to familiarize myself in more detail with the requirements and scope of the project.
Arthur
Budget: 5000 UAH Deadline: 10 days
Hello. I am ready to implement a Telegram bot using Java Spring Boot. Write to me, and we will discuss everything in more detail.
Budget: 5000 UAH Deadline: 4 days
Hello. I have extensive experience in developing Telegram bots (with user roles, databases, and business logic for approvals). I will implement a bot for invoice approvals with a clear distinction of roles: initiator / approver / executor / auditor. The following will be implemented:
- selection of the company (C1, C2, C3)
- input of the invoice with file upload
- approval logic (accept / reject)
- storage of all data in tabular form
- ability to export approved invoices for a period
Budget: 8000 UAH Deadline: 12 days
Good day, we have done a similar project, we can help with your task.
Budget: 10000 UAH Deadline: 10 days
Hello, I can create such a bot. Will these 4 roles have different users for each company?
Write to me, we will discuss the details and final estimate.
Budget: 4900 UAH Deadline: 4 days
Hello
I propose implementation on n8n
Data storage in Google Sheets and in the database
Reminders for all types of users
Checking invoices for "duplicates"
I want to clarify a few more points:
Can each company be the initiator of an invoice or only certain ones?
- verification and adding users?
- assigning user roles
- is the user tied to a company or not
I will be glad to cooperate
Budget: 6500 UAH Deadline: 4 days
Hello, Andriy!
Our IT company creates and refines websites that operate stably, quickly, and solve specific business tasks for clients. We are engaged in developing websites "from scratch" as well as improving existing solutions, enhancing their performance and user experience for your users.
We have experience in:
- developing responsive and fast websites on various platforms (WordPress, OpenCart, Shopify, WIX);
- integrations with payment systems, CRM systems, external services, and internal systems;
- optimizing the performance and security of websites;
- setting up analytics and basic SEO tools;
- software development and automation of business processes: managing customer databases, resource accounting, automating repetitive tasks, integrations with third-party systems;
After completing the project, we provide 14 days of technical support, during which we help adapt the system to your final business processes and consult on any questions regarding the field of work performed. Thanks to the free support of the completed project, this allows you to be confident that the developed solution operates stably from the moment of launch and does not require any additional adjustments.
We work in a structured, responsible manner - focused on results that align with your business goals.
Budget: 5000 UAH Deadline: 7 days
Good day, Andriy
I have extensive experience in developing Telegram bots (see reviews in the profile) so I will gladly help to complete such an important task. However, we need to resolve a few important issues after which we can agree on the budget and deadlines.
Write to me, I will be happy to collaborate. I will be waiting for feedback.
Budget: 5000 UAH Deadline: 5 days
Hello!
The task is clear.
I have experience in creating bots with user roles and approval logic (initiator → approver → executor), with status tracking and data storage in tabular form.
I can implement:
• user registration in the bot in the appropriate role
• company selection (C1 / C2 / C3)
• invoice entry with mandatory fields + file upload
• approval or rejection with date and user tracking
• automatic transfer to the executor after acceptance
• saving the entire history in a table
• auditor access to view/download approved invoices
Implementation through Telegram bot (no code) + Google Sheets
For clarification, I need to understand:
is there one approver or can there be several?
is multi-level approval (sequential) required?
Budget: 5000 UAH Deadline: 7 days
Good day 👋 I am ready to create a convenient Telegram bot for invoice approval — with clear role logic, history preservation, and process automation. We will ensure that:
• invoices do not get lost
• approvals happen quickly
• all history is stored in a table
• audits can be checked for any period
I have experience in creating bots with business logic and process automation. We can think through the structure so that it can be easily scaled for the company. I am ready to discuss the details and propose an optimal solution.
Budget: 5000 UAH Deadline: 1 day
Hello
I am ready to develop a Telegram bot for invoice approval in a group of companies with all the described roles and functions.
Solution structure:
Selection of companies K1, K2, K3 through a menu or buttons.
User roles:
The initiator creates an invoice, enters the recipient's details, amount, subject of purchase, and attaches a file.
The approver receives a notification with the invoice and can approve or reject it.
The executor receives invoices upon approval.
The auditor has access to reports and can download approved invoices for a period in Excel or CSV format.
Technical implementation:
Telegram Bot API using Python (aiogram or FastAPI).
Database PostgreSQL or Supabase, possibly Google Sheets.
Hosting on Render, Railway, or VPS.
Logging of all actions, including dates, roles, amounts, and links to files.
If necessary, a web panel for viewing approvals is possible.
Result: an internal tool for invoice approval with a complete history, archive, and reporting.
Please let me know if integration with the internal accounting system or CRM is needed, as well as in what format files are planned to be stored: Google Drive, Telegram, or locally.
I would be happy to discuss the details and technical requirements.
Budget: 5500 UAH Deadline: 10 days
Good day, we have been developing bots for over 8 years. We are ready to implement it with quality!
Budget: 5000 UAH Deadline: 3 days
Hello! After reviewing your project, I am ready to start working on it. I can offer optimal solutions to achieve the best result.
Budget: 7000 UAH Deadline: 10 days
It's not a difficult task, I am ready to complete it quickly and at a reasonable price, I am looking for feedback in the profile, I am ready to discuss the details.
Budget: 5000 UAH Deadline: 3 days
Good day!
I professionally develop Telegram bots and web applications in Python. I am ready to implement a bot for invoice approval according to your specifications, with experience in integration with Google Sheets/databases. I will deploy it on the server.
Write to me in private messages, and we will clarify the details.
Budget: 8400 UAH Deadline: 7 days
Hello. A bot in Python (aiogram) with 4 roles, company selection (C1–C3), and automatic reports in Excel for the auditor.
Price and terms: $200 for a "turnkey" project, completion time — 7 days.
Result: A complete database of approvals (date, amount, file, status) and automation of invoice transfer from the initiator to the executor.
Budget: 5000 UAH Deadline: 4 days
Hello. The project looks interesting and requires proper implementation. I can create a Telegram bot that will meet all the requirements. I am confident that I can implement all the functions: selection of companies, management of roles for users, and data storage in tabular form. I have a few questions to better understand your needs. What specific integrations are planned, do we need to work with an API? Also, what deadlines do you have in mind for the completion of the project?
Similar project: Разработать Backend для AI веб-сервиса(MVP)
Маю кілька важливих уточнень:
- Кожна з компаній може бути ініціатором рахунку чи лише певна?
- Групи користувачів можуть бути в кожній з компаній чи вони фіксован і заздалегідь відомі?
- Можливість додавати користувачів/компанії теж повинна бути? Якщо так то яка процедура верифікації?
A parser needs to be created to collect competitor prices, with a catalog of over 40,000 products. Access to the prices is only available under authorization.
Good day, I need help with creating the logic and implementing an idea. A chat-bot for tracking the status of document production for an educational center.
Hello. Below is a conditional technical specification for the bot for our synagogue. We need not just a Telegram bot, but a convenient mini-application for the synagogue and community, through which a person can navigate the life of the synagogue, quickly get the necessary information, view the schedule, learn about events, register, and interact with us. In terms of style and logic, we can base it on the reference bot we showed, but we need a better version: more convenient, modern, useful, and with a clearer structure. If you have strong opinions on design, UX, and structure, and you see how to improve it, we are open to suggestions. The main idea: for a person to quickly navigate the life of the synagogue through the bot. What should be in the bot. 1. Main screen with specific buttons The main screen should have clear large buttons: Today Schedule Events Shabbat Jewish calendar My dates A-Yom Yom for today Synagogue services Contacts Donate Settings 2. "Today" section This is one of the main sections. A person enters and immediately sees what is happening today. What should be displayed: what is today's Jewish date what prayers are today what time they take place what events we have in the synagogue today important dates and events in the Jewish world if relevant — time for lighting candles and the end of Shabbat Buttons inside: Prayers today Events today Jewish date Shabbat / candles More details 3. "Schedule" section Through it, a person should conveniently view the schedule. Buttons: For today For tomorrow For the week For Shabbat For holidays What inside: Shacharit Mincha Maariv lessons meals holiday services other activities with time and, if necessary, location It is important that the administration can easily update this schedule. 4. "Events" section A full section on events is needed. What should be included: upcoming events all events card for each event registration In the event card: title date time location short description register button more details button Examples of events: Shabbat lesson youth meeting lecture charity lunch women's / men's meeting holiday outing 5. "Shabbat" section This should be a separate section, not just part of the schedule. What inside: time for lighting candles time for prayers time for meals time for the end of Shabbat weekly Torah portion brief information about the upcoming Shabbat registration for Shabbat Buttons: Upcoming Shabbat Shabbat schedule Weekly portion Register for Shabbat What you need to know 6. "Jewish calendar" section What should be included: today's Jewish date upcoming holidays Rosh Chodesh fasts memorial dates brief explanation of the day / holiday Buttons: Today Upcoming dates Holidays Rosh Chodesh Memorial dates 7. "My dates" section We take this idea from the reference, but want to make it useful. The user should be able to save: birthday Jewish birthday yahrzeit other important dates What the bot should do: store these dates remind about them allow setting notifications Buttons: Add date My dates Reminders Delete date 8. "A-Yom Yom for today" section What should be included: text for today convenient beautiful display ability to view the previous / next day share button Buttons: Today Yesterday Tomorrow Share 9. "Synagogue services" section This needs practical navigation. What can be included: registration for a lesson registration for Shabbat registration for an event ask a question volunteering charity programs other services / directions of the synagogue 10. "Contacts" section Should include: address phone Telegram Instagram YouTube email ways to contact us if necessary, geolocation Buttons: Call Write Open address Instagram Telegram YouTube 11. "Donate" section It needs to be done neatly and clearly. What should be included: donate button payment methods details / link brief explanation of what the funds are for contact for donation questions 12. "Settings" section The user should be able to configure: language daily notifications notification time Shabbat reminders holiday reminders reminders for personal dates Buttons: Language Notifications Shabbat Holidays My dates Enable / disable mailing 13. Daily mailing We need the bot to send people relevant information every day: what prayers are today what time they take place what events we have in the synagogue today what important dates and events are in the Jewish world today if relevant — time for candles / end of Shabbat That is, a person opens the bot in the morning or receives a message and immediately understands the picture of the day. 14. Registrations and sign-ups Through the bot, there should be an option to register for: Shabbat lessons events meetings other activities Logic: a person presses a button leaves their name phone / username if necessary, additional data the application goes to the administrator / to a table / to CRM 15. Admin section It is important for us that the bot is easy to manage. The admin should be able to: update the prayer schedule add and edit events change texts launch mailings see registrations and applications change contacts and links It is important that this is really convenient for maintenance, not too complicated. 16. Support and development At the first stage, it is not necessary to do everything at once; a strong first version can be launched, and then supplemented in the process. But it is important to immediately foresee: the possibility of expansion support and maintenance of the bot after launch bug fixes improvements during use 17. What is important in the end We need a bot that will become a mini-application for our synagogue and help a person navigate conveniently: what is today what prayers what events what will happen on Shabbat how to register how to contact where to view the Jewish schedule what is happening in our synagogue and in the Jewish world If you see how to make the structure, buttons, design, and logic better than in the reference bot, that is a plus. We need not a clone, but a stronger, more convenient, and modern version. https://www.hebcal.com/home/developer-apis Chabad.org
Development of a Telegram bot: a closed platform-marketplace for experts I am looking for a developer (or a small team) to create a Telegram bot — a closed platform that connects verified experts and clients for solving professional tasks. The model is similar to a service marketplace with a supervising administrator, rather than a fully automated service. What is ready: A detailed technical specification (30+ pages) — user roles, step-by-step UX flows with button texts, status models for Requests/Cases, data model, payment status model, admin panel. Key functionality: - Two user roles (client / expert) with the possibility of combination - Verification of experts through the administrator (without automatic decision approval) - Selection and moderation of requests by the curator - Internal communication space within the bot (without disclosing contacts between parties) - Payment status model: escrow, confirmation of funds receipt, payments - Referral system with bonuses - Administrative panel with extended access rights Expected stack: at the discretion of the developer (Python/Node.js), the main thing is — experience with Telegram Bot API, working with states (FSM), databases, and payment integrations. Collaboration format: work based on the ready technical specification, discussion of deadlines and budget after reviewing the document. What to send: examples of implemented Telegram bots (preferably — with complex state logic or payments), an estimated timeline and cost.
Technical assignment for the client search automation system in Telegram Development 1. General task It is required to create an MVP system for automatic client search in Telegram chats with the provision of found users to sales department operators. The system should consist of: user bots based on Telethon; Telegram bot for operators; Telegram bot (or a separate administrative section within the bot) for the administrator; PostgreSQL database; Docker configuration for deployment in configuration. A web panel is not required at this stage. 2. Working with multiple Telegram accounts The system must not be limited to one Telegram account. It is necessary to ensure support for multiple accounts (for example, 5 or more) with the ability to increase their number without changing the configuration. For each account, there should be the ability to: authorize via Telethon; maintain its own session; connect a new account; disconnect an account; replace an account without losing the database. The administrator should be able to independently connect new Telegram accounts. 3. Distribution of chats among accounts The system will use a large number of Telegram chats (approximately 800 or more). All chats are included in a single system. The system should automatically: manage chats among connected accounts; observe Telegram restrictions; Handle the need to transfer a chat to another account; Prevent duplication of one chat by multiple accounts (unless specifically included). It is desirable to ensure load balancing among accounts. 4. Managing the chat list The administrator should be able to do this without the developer's involvement: connect a chat; delete a chat; import a list of chats from a file; bulk upload chat costs; enable or disable monitoring of individual chats; restart history collection for a selected chat. After adding a new chat, the system automatically includes it in one of the key accounts. 5. Data collection For each connected account, it is necessary to implement: Initial parsing After adding a chat: loading message history for the specified period; saving all available information. Monitoring After the initial loading is completed: constant tracking of new messages; saving new users; saving new activity of existing users. 6. Handling Telegram blocking requires proper handling: FloodWait; PeerFlood; temporary Telegram restrictions; erroneous connections; connection breaks; possible reconnections; temporary unavailability of the account. If one account is temporarily blocked by a restriction, the rest of the work continues. 7. User data storage. For each user, the following should be saved: Telegram ID; first name; last name (if available); username; profile link; list of all chats; message text; date and time of the message; link to the message (if obtainable from Telegram). User merging is performed exclusively by Telegram ID. If a user has written in 20 chats — they display one card. 8. User card The operator should see: first name; username; Telegram ID; profile link; list of all chats; messages; activity date. Example: User: Ivan Ivanov ID user : 123456789 Chat "Business": Message: "Good day, interested in advertising" Date: 01.03.2026 12:15 Chat "Marketing": Message: "Who is handling promotion?" Date: 05.03.2026 18:42 9. Operator work The system should automatically form a queue of clients. After receiving a client: the user is assigned to an operator; the second operator cannot receive the same client; maintain a history of actions. Statuses: Took the client; Unavailable; Could not reach; Refusal; In progress; Call back; Delete. After selecting a parameter, the next client will automatically open. 10. Reissuing users There should be an option to configure user reissuance. For example: never; after 30 days; after 60 days; after 90 days; arbitrary period. 11. Administrative section The administrator should be able to: Account management add an account; delete an account; view account status; view account restrictions; replace an account. Chat management add; delete; import; export; disable monitoring; disable monitoring. Operator management add; delete; block; change rights. Parser management start collection; stop collection; rebuild history; view current status. Statistics View: number of users; number of messages; number of processed clients; number of active operators; number of connected accounts; number of active chats. 12. Database Use PostgreSQL. It is necessary to store: users; messages; chats; activity; Telegram accounts; operators; processing statuses; processing history; distribution of chats among accounts. 13. Scalability The architecture should provide the ability to: connect 10, 20 or more Telegram accounts; connect thousands of Telegram chats; handle load; export data; work with CRM; connect new features without a complete project overhaul. 14. Docker The executor should set up: docker-compose.yml; Dockerfile; launch instructions; update instructions; database backup instructions. The system should manage the command as one.