Skip to main content

Community

Connector Improvement: Zip Connector more fields

Planned

Please sign in to leave a comment.

Comments

3 comments

  • Official comment

    Hi Ashveen,


    This feature request to expand the Zip connector to include additional fields has been added to our backlog for connector improvements. The idea is noted as valuable, and we recognize the potential benefits of making more data accessible from Zip.


    To better prioritize and scope the work, could you share more details about your use case? For example, what problem are you trying to solve by including these specific fields, and how would access to this data help your team?


    We will keep the community updated on this thread with any progress or changes related to this request.


    Thanks,
    Unnikrishnan

    Our main use case is automating payables accruals in our data platform using Zip as the source of truth, instead of relying on manual Zip report exports every month.

    Today, our Accounting team uses Zip’s own custom export reports (open PO, bill line, credit memo, etc.) that already include the requested fields (e.g. invoice line amortization fields, PO line amounts and identifiers, request‑level attributes like region/partner type). Those fields are essential to:

    • Reproduce the same accrual and amortization logic programmatically.

    • Do line‑level analysis and reconciliation by PO line, project, region, and partner.

    • Eliminate manual CSV downloads while keeping the process consistent with what Zip exposes in its UI/reports.

    Exposing these fields in the Zip connector would let us move that existing month‑end workflow fully into our data warehouse automation. Databricks has $5.4bn ARR with 65% YoY growth - it is imperative for us to automate this process as we cannot rely on manual processes at this scale. Current process requires multiple people to perform this process manually.

    Thanks for the inputs Ashveen. 
    Our team is actively working on this - we will be reaching out directly for additional inputs.

    Regards,
    Unni