Skip to content
cccskills
FreePublished on GitHub

mydata-invoicing

Issue Greek invoices through AADE's timologio, get the MARK, keep one JSON per invoice, push it into the ERP (SAP Business One today; other adapters welcome) and email the PDF. Trigger on: τιμολόγιο, τιμολόγησε, έκδοση τιμολογίου, invoice, myDATA, timologio, MARK, ΤΠΥ, πελάτης ΑΦΜ, προεπισκόπηση τιμολογίου.

The English summary is being prepared. Showing the original description.

See how to install

Files included (24)

  • SKILL.md3.1 KB
  • .env.example627 B
  • .github/ISSUE_TEMPLATE/adapter.md814 B
  • .github/ISSUE_TEMPLATE/timologio-breakage.md447 B
  • .github/PULL_REQUEST_TEMPLATE.md296 B
  • .gitignore124 B
  • adapters/__init__.py0 B
  • adapters/epsilon_pylon.py984 B
  • adapters/megasoft.py974 B
  • adapters/sap_b1_api.py29.6 KB
  • adapters/sap_b1.py7.7 KB
  • adapters/softone.py9.3 KB
  • config.example.json1.1 KB
  • CONTRIBUTING.md1.5 KB
  • docs/adapters.md3.4 KB
  • docs/invoice-schema.md3.6 KB
  • docs/timologio-endpoints.md3.5 KB
  • examples/invoice.example.json2.6 KB
  • LICENSE1.1 KB
  • README.md14.5 KB
  • scripts/invoice_store.py7.6 KB
  • scripts/issue.py8.4 KB
  • scripts/mydata_api.py12.0 KB
  • scripts/timologio_client.js7.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

myDATA invoicing (timologio + ERP)

ROOT = this folder. Run everything with python3 ROOT/scripts/issue.py .... Config in ROOT/config.json, credentials in ROOT/.env (never read aloud, never printed).

Preconditions: Chrome with the user logged in at https://mydata.aade.gr/timologio. The browser client is ROOT/scripts/timologio_client.js; inject its full text with the JavaScript tool into the timologio tab after every navigation.

The rule

Three actions are irreversible: TL.issue(), issue.py erp --yes, sending the email. Each one happens only after the user has seen the result of the previous step and said «ναι» in the chat. Never chain them without that.

Flow

  1. issue.py new --vat <ΑΦΜ> --item <key> --net <amount> [--descr] [--notes] [--payment] Prints the draft id and a SPEC json.
  2. Customer unknown to timologio? Open /timologio/customer/NewCustomer, inject the client, TL.createCustomer(vat, email) fills it from the tax registry. Show the data, then TL.saveCustomer(). Record the code from the green banner: invoice_store.save_customer(vat, timologio_code=N, name=..., street=..., ...).
  3. Open /timologio/invoice/newinvoice, inject, await TL.build(spec). Check totals against spec.expect. await TL.preview(), TL.showPdf(), screenshot, show the user. issue.py previewed <id>. TL.hidePdf().
  4. Wait for «ναι». await TL.issue() → {mark, aa}. At once: issue.py issued <id> --mark <mark> --aa <aa>.
  5. Navigate the tab to https://mydata.aade.gr/timologio/Invoice/PrintInvoice2PdfNew?mark=<mark> (it downloads). issue.py pdf <id>.
  6. issue.py erp <id> --dry-run, show the body. On «ναι»: issue.py erp <id> --yes. Report DocNum and the myDATA duplicate check.
  7. issue.py email <id> → to / subject / body / attachment. Send from Gmail in Chrome: open https://mail.google.com/mail/?view=cm&fs=1&to=<to>&su=<subject>, click the body, type it, upload the PDF with the file-upload tool on the compose file input, click Send. Then issue.py emailed <id> --to ... --to ....

issue.py list shows every invoice with MARK, ERP document and state.

When things fail

  • TL.build returns {error}: read it, fix the input, btnClear, retry. Do not issue.
  • Preview PDF shows wrong amounts: stop, ask.
  • issue() returned no MARK: check /timologio/invoice/listinvoices before retrying; a second issue creates a second invoice.
  • ERP post failed after issuance: the JSON stays issued. Fix and rerun erp --yes; the adapter will not double-post.
  • myDATA check shows 2 documents: the ERP connector re-sent. Cancel the extra MARK in myDATA, then set the ERP's "transmitted" flag by hand and note it in the audit.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Report a problem with this skill