Skip to main content
All learning experiences

Technical Writing & Software Documentation

Biller Portal Guide for Software Partners

Technical Writing & Software Documentation · InvoiceCloud

A 44-page technical guide for software partners using InvoiceCloud's electronic billing and payment platform, translating complex system functionality into task-focused documentation.

  • Microsoft 365

Project overview

This 44-page technical guide was developed for software partners using InvoiceCloud's electronic billing and payment platform. I translated complex system functionality into clear, task-focused documentation covering customer and invoice management, payment processing, AutoPay and recurring payments, reporting, reconciliation, data integrations, API-related configuration, email management, and user permissions.

The guide combines procedural writing with interface screenshots and visual guidance to help users understand both what system features do and how to use them. The project demonstrates my ability to learn complex software, organize substantial amounts of technical information, and translate that knowledge into practical documentation for users and software partners.

Audience

Software partners and their support staff working directly in the biller portal, alongside internal teams who assist them.

Learning need

Not every performance need requires a course. Technical documentation can provide durable, searchable support at the moment of need.

Partners work in the portal intermittently and across many different tasks, so the right solution was reference material they could return to rather than training they would have to remember.

Instructional design rationale

The guide is organized around common portal functions and the tasks software partners perform within them, so someone can find the section that matches their situation instead of learning the system's internal organization first.

Each procedure pairs written steps with the interface it describes, which is what makes documentation usable at the moment of need rather than only during a read-through.

Not every performance need requires a course. Sometimes the right solution is durable, searchable documentation.

Design decisions

Organized around common portal functions and partner tasks
Partners arrive with a job to do. Grouping procedures by portal function and the tasks performed within it helps them find the relevant answer quickly.
Screenshots paired with each procedure
Written steps alone leave room for interpretation. Showing the actual interface removes it.
Technical depth kept where it belongs
Data Pump concepts, response statuses, and troubleshooting sit in their own section so routine users are not slowed down by material they do not need.

Document preview

Portfolio presentation: this case study displays a curated six-page excerpt from the original 44-page guide. The selected pages show representative examples of procedural writing, interface documentation, multi-step workflows, and more technical Data Pump content. The complete internal guide is not publicly distributed.

Excerpt page one: audience framing and software access guidance for the biller portal.
Page 1Audience framing and software access guidance
Excerpt page two: customer search and interface documentation with annotated screenshots.
Page 2Customer search and interface documentation
Excerpt page three: transaction-processing instructions with step-by-step guidance.
Page 3Transaction-processing instructions
Excerpt page four: step-by-step AutoPay enrollment guidance.
Page 4Step-by-step AutoPay enrollment guidance
Excerpt page five: Data Pump reporting documentation.
Page 5Data Pump reporting
Excerpt page six: Data Pump concepts, data exchange, response statuses, and troubleshooting.
Page 6Data exchange, response statuses, and troubleshooting

Selected six-page portfolio excerpt shown. Full documentation is not publicly distributed.

What this project demonstrates

  • Technical writing and software documentation
  • Information organization at scale
  • Performance support as an alternative to training
  • Visual documentation of software interfaces
  • Translating complex software into understandable instructions

Related projects

Title screen from the Ethical and Inclusive AI in Online Course Design walkthrough recordingeLearning / Articulate Rise 360

Articulate Rise 360 + Storyline 360

Ethical and Inclusive AI in Online Course Design

Graduate Instructional Design Project — University of Memphis

A longer, more scaffolded course on ethical and inclusive AI use in online teaching, built in Rise 360 with a custom Storyline 360 branching scenario embedded where decision practice was needed.

  • Articulate Rise 360
  • Articulate Storyline 360
View Case Study
Opening screen from the Navigating Public Transportation in Memphis course walkthrougheLearning / Articulate Rise 360

Articulate Rise 360

Navigating Public Transportation in Memphis

Community Education — Friends For All

A streamlined Rise 360 course helping adult community learners build confidence using public transportation in Memphis, with interactions chosen to reduce cognitive load rather than to demonstrate complexity.

  • Articulate Rise 360
View Case Study
Opening screen from the Smart Shopping course walkthrough recordingeLearning / Articulate Rise 360

Articulate Rise 360

Smart Shopping: Practical Skills for Everyday Savings

Community Education — Friends For All

A Rise 360 course giving adult community learners low-risk practice recognizing and applying practical shopping strategies in everyday purchasing decisions.

  • Articulate Rise 360
View Case Study

Get in touch

Questions about this project?

I'm glad to walk through the analysis behind the decisions, or how I'd adapt this approach to your organization.