Şentürk Otomotiv

The problem

Incoming invoices went from hand to hand: who saw them, who approved them and where they were waiting could not be tracked. Late approvals delayed payments, and because the accounting entry was manual, the same invoice could be posted twice.

What I built

I built a flow that takes the invoice and its document into the system and creates an approval chain by amount and department. Approvers see it on their screen and write a reason when they reject. Approved invoices are posted to Logo through the integration, with duplicate checks in place.

• Invoice record with its document attached
• Approval chain by amount and department
• Approval and rejection history with reasons
• Posting to accounting through the Logo integration
• Duplicate invoice checks
• Access levels and pending-approval notifications

The result

The approval process left paper behind; the stage of an invoice and whose desk it waits on are visible on one screen. With posting automated, duplicate records and manual entry errors are gone.