Project description
TranslatedOur company issues dozens of invoices, service agreements, and work status reports weekly, and currently employees manually transfer numbers into Word, adjust the layout, and export each file to PDF one by one. The process is slow and small errors in amounts, dates, and document numbers slip through too often. We are hiring a developer to build a document automation pipeline: it takes our data from a table or from an internal API and outputs ready-to-use branded PDFs without manual editing. The template design, logo, and color scheme are already prepared and will be provided at the start of work.
The solution should read structured input data (rows for invoices, contract parties, and line items), substitute them into pre-defined templates, and generate a neat PDF. Each document type needs its own template, but they all must have a unified visual style: identical headers and footers, fonts, margins, and color accents so the entire set looks like a product of one brand. We expect dynamic fields that substitute customer names, addresses, dates, and amounts, repeating line item tables with automatic subtotal and tax calculation, and continuous document numbering without gaps or duplicates. The system should run on demand and on schedule, place finished files in a shared folder, and maintain a log of what was generated.
Please describe your approach, which libraries or tools you will use, and how to make templates convenient for editing by non-technical staff. We value clean, documented code and reliable numbering most of all. What we expect to receive:
— A working generator that produces invoices, contracts, and reports in PDF from table and API data
— Reusable templates with dynamic fields, repeating tables, auto-totals, and unified branding
— Automatic continuous numbering with a safe counter without gaps
— On-demand and scheduled execution with logging and basic error handling
— Brief documentation so the team can edit templates and add new document types
The solution should read structured input data (rows for invoices, contract parties, and line items), substitute them into pre-defined templates, and generate a neat PDF. Each document type needs its own template, but they all must have a unified visual style: identical headers and footers, fonts, margins, and color accents so the entire set looks like a product of one brand. We expect dynamic fields that substitute customer names, addresses, dates, and amounts, repeating line item tables with automatic subtotal and tax calculation, and continuous document numbering without gaps or duplicates. The system should run on demand and on schedule, place finished files in a shared folder, and maintain a log of what was generated.
Please describe your approach, which libraries or tools you will use, and how to make templates convenient for editing by non-technical staff. We value clean, documented code and reliable numbering most of all. What we expect to receive:
— A working generator that produces invoices, contracts, and reports in PDF from table and API data
— Reusable templates with dynamic fields, repeating tables, auto-totals, and unified branding
— Automatic continuous numbering with a safe counter without gaps
— On-demand and scheduled execution with logging and basic error handling
— Brief documentation so the team can edit templates and add new document types
Web programming Cash, Bank transfer
